OK, so here's the deal.....I did a little experimenting awhile back and found that booting Windows 10 in UEFI mode on MBR partitioning works fine (http://reboot.pro/to...-gpt-very-easy/). My Samsung SSD is MBR-partitioned, and has a FAT32 EFI system partition, marked with the "EFI" flag in GParted. All runs fine, drivers install, updates install, games work, no BSODs. I chose MBR because this will allow me to boot legacy OSes as well. And I can use softwares like rEFInd and Clover for UEFI booting. I imagine that Linux should generally work fine on this setup too.
But now I have the issue of wanting to boot 10 in legacy mode. This of course requires the appropriate boot files, and an appropriate MBR. But if Clover's code (or whatever) is to occupy my disk's MBR, then Windows' MBR cannot live there too. So I'm thinking that maybe there is a way to chainload the Windows MBR, from something like GRUB4DOS, then it loads the Windows boot files, and (hopefully) 10 boots without BSODing.
I will also note that my C drive is encrypted with BestCrypt Volume Encryption, which to my surprise worked without a hitch. But if I am to boot 10 in legacy mode, then I will need to use the appropriate BC MBR so that it can decrypt and boot the C drive. This is another barrier that needs to be considered.
On a side note, I used the following command when installing 10, after installing the OS with imagex:
bcdboot C:\Windows /l en-US /s A: /f UEFI
C of course represents the C drive, A represents the letter I assigned to the EFI system partition. Valid options for /f are UEFI,BIOS, or All. I had tried the "All" option in the past and hit issues with BestCrypt and GRUB2.