11.2 Kernel Watchdog Timeout in "com.apple.remoted" Using Samsung T3 SSD

[Takuro]

So I have a really bizarre issue.

• I've been test driving macOS Big Sur for a couple months now using a Samsung FIT Plus 256GB USB thumb drive. It's worked totally fine during the entire time, albeit pretty slow.
• I had a spare Samsung T3 external SSD sitting around, which is also 256GB. So I decided to install Big Sur to that and used Carbon Copy Cloner to migrate the "Data" container from the FIT Plus to it.
• The Samsung T3 acted like a total clone of the original drive as expected. I shut down the computer, rebooted to Catalina a few times, and booted back into the T3 to use Big Sur multiple times. No issues.
• Totally at random, the T3 drive would stop booting. It would load about half way at the Apple logo, hang, and crash. Booting into verbose mode, it looks like it's hitting a watchdog timeout with com.apple.remoted.
• Even more bizarrely, this watchdog timeout is only happening on my 2020 27" iMac. If I plug the T3 into any other Mac or boot it via Parallels emulation, it boots into macOS just fine.
• I decided to erase the drive, reinstall/upgrade to macOS 11.2 this time, cloned the "Data" container as I had before, and the drive continued to work normally for a few days and then suddenly encountered the exact same issue again.
• On my 3rd attempt, I decided not to erase the drive entirely and just reinstalled macOS. However, it still fails to boot, so it must be something in the "Data" container causing the problem. Maybe some 3rd party software or a kext.

Also worth noting here for the sake of disclosure:

• I do have csrutil disabled on my iMac and all other machines I've used this T3 drive on. This is because I still use kexts, which I know are depreciated in Big Sur. I'm using kexts for Paragon NTFS, Little Snitch v4, and Adguard. I have not tried with these disabled, but it wouldn't make sense for them to be the cause since the Samsung FIT drive works fine with those also.
• I do have SSV disabled on my iMac and all other machines I've used this T3 drive on. I am using this to overwrite system files to customize app icons. However, again, it doesn't explain why the Samsung FIT drive is fine doing the same. Also, the boot issues never seem to have a strict cause/effect of happening after I commit a custom snapshot to the system container. The boot issue happens totally at random even when I haven't messed with system files.

I am really at a loss here. The only major difference between the Samsung T3 and the Samsung FIT drive is that the T3 only has 40GB of space free because I later installed Xcode. I know that there's been recent reports of Big Sur corrupting itself if a disk runs out of space, so my only thoughts are to do all my tests again but make sure Xcode is not installed so the T3 drive has about 70GB free like the FIT drive.

But what I sincerely can't wrap my head around here is: If it is disk corruption, why does the same T3 drive boot fine via Parallels and with a 16" MacBook Pro? It only happens on the 2020 iMac.

I'm attaching screenshots of the T3 drive failing to boot and the kernel panic log that got dumped after I booted back to Catalina. I don't personally see anything too interesting. Also my apologies for how blurry the 2nd screenshot is -- my phone's camera couldn't keep up well with the rate the text was being printed.