I do not think migrating of drivers, apps and settings from failed system is
a good idea (besides it is near impossible to do).

Better to try to solve your IBD error once more. Usually it is not too hard.

Common IBD errror is caused by improper change of BOOT.INI file, partition
structure, disk physical or logical order, BIOS version or settings or
Windows disk driver (one of runtime and loader driver or both). It can be
caused also by  too long partition, too fragmented NTFS internal tables
(NTFS partitions only),  by too high version of NTFS (again NTFS partitions
only). And, at last, also by physical failure of disk or disk controller
(but it is very uncommon cause).

As you have another running version and access to old version, you can
compare content of BOOT.INI files as wrong BOOT.INI is the most frequent
cause of IBD error. This does not mean that original BOOT.INI is incorrect,
but BOOT.INI should follow changes made in BIOS setttings and partition
structure. If you do such changes without updating BOOT.INI records, you
often will end up with IBD error. In case of BIOS settings it is also
possible they changed itself to BIOS defaults due wrong battery or any power
incident. BOOT.INI file is located in root of C: partition and you should to
turn off hidding of system and hidden files (and in W2K a WXP also hiding of
system protected files) in View menu options of Windows explorer to see it.
if there are records starting by scsi() in BOOT.INI, look also for file
ntbootdd.sys in root of C: partition of both disks and compare, if they are
identical (it is optional disk driver used by NT loader).

Note that if you have not original system patched to SP6a and your
partitions are NTFS, you are now on dead end because Windows NT without SP6
cannot access NTFS partitions touched by Windows XP. The only solution in
such case is to backup whole thing, repartition and reformat it under
another NT system and then restore from backup. With two disks you can do
also direct copy, there are tools like robocopy and scopy in NT resource kit
able to help you with this task. This method can also solve problems with
too fragmented NTFS and too long partition (even in such case I am
recommending to repartition your system to fit NT official requirements).