Well I know what's causing the bricks.
So i figured out in part at least what is indeed causing the bricks. It was my first guess, but I messaged a couple of kernel devs, and the information they gave me led me to believe my first assumption was wrong. Apparently it was not. i am not sure if it's an aosp thing, a twrp (was using 22.214.171.124) when I found out, or just a really nice user error experienced by a handful of people. But regardless, either the kernel, and or some of it's settings are not being wiped in twrp to include an advanced wipe of all check boxes besides usbotg, a format data, and then a factory reset wipe. So when kernel or settings interact with new kernel/rom that you install and they don't play nice together, you get your nice little brick. Oh but how do I come across such preposterous conclusions you ask yourself? So I payed my 50 bucks, got my new phone, put my go to rom on it, and play away; lo and behold a stable 10.1 cm comes out. Can't resist, must flash, disapointing to see in the stable release the first thing I have to do is edit build prop to get sprint signal(it is a sprint rom yes?) Still liking the rom for what it is, probably my favorite, except Trebuchet is laggy as S**t(ping pongs kernels alleviate this, but his kernels are for 10.2). So in an attempt to fig the lag, i play with different settings and whatnot that I found laying around xda here and there. nothing is helping with the stutter I see on the home screen. So I go to the main One thread, and look around for kernels, I find one, don't figure it will work, but figure I'll just wipe if it does bad things to my phone; and it did. 8 boot loops later what do I do? Wipe everything as mentioned above, and sideload 10.1 stable, guess what happens on reboot? That's right bootloops. So some how the kernel or some of it or its settings at least are not going away as they should on a clean install, and that I'm sure is what is causing the bricks.
I'll be here all night