NVMe not detected during Debian Preseed on some boards

[mgcdrd]

Long explanation on this one and doesn't match other existing issues.

Basic explanation:
I ordered 8 DEV Computer blades and have been working on utilizing my existing lab's infrastructure to be able to provision OSs on to them. So far 3 are able to be provisioned with Debian 12 ARM64 using a slightly modified preseed file. 5 of them are hitting the exact thing during preseed - "Detecting hardware" takes a while and then proceeds, and the whole thing then hangs at 8% on "Starting up the partitioner".

Troubleshooting performed so far:

• tested preseed against several x86-64 systems, no issues for them
• Swapped NVMe, microSD, and CM4 between working and none working boards - issues remain on the 5 boards
• Swapped provisioned NVMe to affected boards, and was able to boot into the OS on the NVMe
• Resat NVME. microSD, and CM4 on affected boards multiple times with varying tightnesses on CM4 screws
• Reflashed EEPROM
• Rebuild microSD with pftf/RPi4; copied working disk and files

Hardware:

• Compute Blade V1.0 Mk4-K
• Compute Module 4 8G Lite
• TeamGroup TM8FP6256G0C101
• SanDisk Industrial 8G

Software/Firmware of Hardware:

• EEPROM - usbboot current master branch
• pftf/RPi4 v1.42

Contents of EEPROM boot.conf

[all]
BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0

# Boot Order Codes, from https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#BOOT_ORDER
# SD card, then NVMe
#BOOT_ORDER=0xf1
BOOT_ORDER=0x61

# Set to 0 to prevent bootloader updates from USB/Network boot
# For remote units EEPROM hardware write protection should be used.
ENABLE_SELF_UPDATE=1

I can provide the pftf/RPi4 configs, but seeing as all of them are configured the same (besides boot order), those should have no affect.

The oddity I can't wrap my head around is the preseed environment won't detect the NVMe only on specific boards, but the UEFI firmware sees them, and will boot from them. Sadly, once the Linux kernel picks up, USB stops working so I can't troubleshoot from within the environment itself.