[Samsung Galaxy S 5 Unified Development] FNetV1:
I would like to add to my previous post that I performed additional diagnostic:

On the EFIDroid menu I selected TWRP then chosed the "Exodus_Marshmallow" entry, I completely wiped it, then restored a nandroid that I had created when I was running MOAR 2.2 Kitkat ROM. Aside from the fact that the restore was painfully slow (over 4 MB/s to restore over 3 GB) and took like an hour to complete, the ROM booted, it went past the boot screen and the home screen did loaded with the following exception:

There was no signal in the signal bar indicator where usually it would say "LTE" right after boot up and having reached this screen.

Then in about 5 more seconds I saw my first app FC, after I acknowledged the "xxxxxxxx app has unexpectedly closed" by clicking on the OK button another app FC one after the other, lets call it an app FC marathon where every app just FC. Pressing the home button caused the whole screen to black out followed by "touchwiz has unexpectedly closed" and this error would come up each time I pressed the home button.

Well, I restarted the phone (the restart menu was working, about the only thing that was working under this environment), on the EFIDroid menu I selected TWRP and the ROM. I wiped everything and proceeded to install MOAR 2.2 KitKat freshly. After going through a buggy flicking AROMA installer and selecting all my options, the installation went thru just fine. I restarted the phone, under EFIDroid I selected this ROM, and to my surprised the blinking "Android" logo just stood there, just like my previous two experiences with my native stock lollipop rom, followed by Exodus Marshmallow, this too refused to boot past showing its boot logo and playing the startup music (about 3 seconds after having showed the boot logo) then nothing after that.

Once again, it was back at removing EFIDroid, flashing /boot from my original stock nandroid backup for my phone to work normally again.

Based on my observation with my MOAR KITKAT nandroid restore observation where I did got a PARTIAL successful boot to a home screen, and I saw PARTIAL because even though it completed boot up as in from going from the animated boot logo to actually seeing my home screen's JPG image and the status bar indicated "no signal" and other icons, I got a torrential FC as a nasty side effect and this only materializes after having restored this nandroid backup within an EFIDroid environment. But if you do a proper, right of a bat installation of the very same ROM (MOAR KITKAT) then it refuses to boot. Therefore I believe that EFIDroid should be fixable for the kltespr / G900P or should I say CDMA variations because if its fixed for the kltespr, then I believe it should also work for the kltevzw.

*I believe at the moment I have tried everything I could possibly try and all possible combinations such as enabling "force SELinux permissive...." for all ROMs, short of flashing an older bootloader, but I dont think that flashing Kitkat's bootloader/baseband would actually help solve anything.

Here's my best guess based on the behavior I have seen so far:

The ROM's (including stock) are having trouble accessing or initializing the CDMA modem/radio when loaded from within the EFIDroid environment due to something EFIDroid did upon its installation or its method of working that created some problems over there, since an article I read that explained in technical terms how EFIDroid works, that it works by using some QUALCOMM features/function, well QUALCOMM is the radio, so maybe there lies the problem why this is not or refusing to work properly for the kltespr (and the kltevzw).