Redeploy of Win10 Os from old computer to new computer Dual Boot with seperate drives

[TerribleCoder]

This a partial copy of my post on the Macrium Forum because I used Macrium Reflect Home to do an image restore/redeploy

I have a newer desktop computer on a NVMe drive running Win 10 Pro 64 bit along with several other mechanical hard drives for data plus a SSD drive.
A have another older computer running dual boot Win 10 Pro 64 bit and Win 10 Pro 32 bit (the earliest machine)  each OS on separate drives.
My plan was to redeploy the old computer Win10 Pro image onto the SSD drive of the newer computer and thus make a dual boot of two Win 10 Pro Systems on separate drives (new machine Win 10 is on the NVMe drive)
in the new computer.   I am doing this because each system has unique programs and configurations that would be impossible to transfer to the latest Win 10 system.

However, what I did was restore the entire partition structure of the old  Win 10 Os on the new SSD drive of the newer computer with Macrium restoring from a backup of that Win 10 Os.
I injected the new disk drivers with redeploy.     However I realize that the boot information on the old dual boot computer resided on the Win 10 Pro 32 bit OS drive, which doesn't come across in
the image restore.
I can boot the Win 10 on the NVMe drive but if I try booting the old system I get a missing winload.efi error, which is really a signal that the effectively cloned EFI boot info for the old Win 10 Pro OS
is not there or has remnants that worked with the boot manager running from the old dual boot computer's boot off the Win10-32bit machine.
Here is a picture of a map of the drives:

The partition on disk 1 that is named Win7-64 bit is actually the older Win 10 Os from the other machine, as it originally was a Win 7 machine that got upgraded.
Disk 3 is the NVMe drive with the latest Win 10 Pro build that still boots and works.

I have USED THE MACRIUM BOOT REPAIR FUNCTION TWICE, BUT IT CANNOT FIX Disk 1 to boot.

I do not want to use the  dual boot repair tool, until I  understand what is wrong before I attempt to use the tool.   I have backups of both systems up to date.

Other perspectives on similar configs are here:
https://answers.microsoft.com/en-us/windows/forum/all/how-to-install-two-windows-10-os-in-two-seperate/def4fdd8-715f-4cb1-8586-2416325efa14
and here:
https://answers.microsoft.com/en-us/windows/forum/all/installing-windows-10-on-two-different-drives-on/6cbb6f55-bfb0-411a-8fbd-bd987b02474f

I understand that I could have unplugged the NVMe card when I tried to redeploy the older Win Pro on the SSD and then reinserted the card and rebuild the boot menu.

I ran into a similar problem once before on booting the newer single Win 10 Os and used bootrec as described here:  

 https://coverjunction.com/fix-bootrec-fixboot-access-is-denied-on-windows-10/

But I really did not understand exactly what I was doing besides mimicking the commands.

Any suggestions or references to articles online would be appreciated.

[TerribleCoder]

I also forgot to mention:

The older computer that ran the old Win10 Pro OS did not have a UEFI bios.
The new computer does have a UEFI bios, but for some reason I need to keep the bios in legacy boot, otherwise the system won't boot at all.​

[TerribleCoder]

Output of BcdEdit

C:\WINDOWS\system32> bcdedit /enum /v

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {465f9141-ac25-11ed-9920-c86000395264}
resumeobject            {465f9140-ac25-11ed-9920-c86000395264}
displayorder            {465f9141-ac25-11ed-9920-c86000395264}
                        {465f913f-ac25-11ed-9920-c86000395264}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Windows Boot Loader
-------------------
identifier              {465f9141-ac25-11ed-9920-c86000395264}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {465f9140-ac25-11ed-9920-c86000395264}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {465f913f-ac25-11ed-9920-c86000395264}
device                  partition=\Device\HarddiskVolume9
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=\Device\HarddiskVolume9
systemroot              \Windows
resumeobject            {465f913e-ac25-11ed-9920-c86000395264}
nx                      OptIn
bootmenupolicy          Standard