Update. I'm not sure what made the original Sabrent SSD glitch out which is why I added another 2tb nvme m.2 drive, but I may have found a reason for the weird behavior with both SSDs in.
The EFI partition was still on the Sabrent drive and not on the same drive as my windows install. (because I guess the Sabrent was still installed when I installed my Kingston 2TB, and it somehow still read the partition when I installed Windows again on the new SSD even though it wouldn't boot from the Sabrent?? confused, I am)
I just fixed all that with this: https://www.tenforums.com/installation-upgrade/52837-moving-recreating-efi-partition.html
Fingers crossed- this helps resolve the issue.
But it's something to check if somebody has similar issues.
But then again, I have no idea if that would even cause an issue like what I was having.
Anybody here know if having the EFI part on another drive than the main OS would cause an issue?
I noticed it because I wanted to wipe the Sabrent and use it as a 2nd drive for just my games. Damn games are big today.
It had started working again so I was dual booting to access something I had on the old OS drive...