TSM has always been quite happy to having a DB restore done to a clean
system.
I have moved servers that way more than once. (And recovered a couple of
dead ones).

If you don't delete the disk pool volumes before you back up the DB, TSM on
the new system gives you a polite error message at startup time saying it
can't find them.  But I've never had a problem cleaning that up after the
fact.

Remember that before you start, your DB and LOG on the new system must be AT
LEAST AS LARGE as on the system that did the DB backup.  The configuration
of the new DB & log (e.g., the number/names of DB volumes) don't have to be
the same, it just has to have at least the same total GB.

However, I don't think Tivoli ever totally  guarantees that a data base
created at one level can be restored into a server at the next level.  I
called once about that, and the answer is "it should work".  And it should,
and I've done it more than once.  But I don't think Tivoli tests every
combination of old-db-restored-to-higher-level, so they don't guarantee it.
When possible, I upgrade the old system IN PLACE before doing the DB move.
It's just a simple SMIT install, and might save grief if it's convenient to
do.

Also, "4.1.x" is not a good idea if x=0.  I'd upgrade the target server
first to 4.1.3.