Heads up: I wrote most of this, left to eat, then came back and found other issues as well as the cause of most of them. So it might be a little all over the place due to rewriting.

For the past few days, I've been unable to open a tty after launching X. When I switch to tty from X, the monitor goes black and displays the message that it's receiving no input signal. This only happens when going from X to a tty though. However, from tty1 at login, I have no issue switching to the different ttys and I have no issue using any tty before X launches. But killing X from my desktop results in the shut off monitor (though I can still login) and changing from the desktop to tty{2..12} brings it about as well.

The other issue I encountered is the inability to mount my two EXT4 SATA SSDs. When I attempt this with

# mount /dev/sda1 ~/Games/Drive1
# mount /dev/sdb1 ~/Games/Drive2

I get the error `wrong fs type, bad option, bad superblock` for both commands.

Both of these errors seem to be related to my custom kernel, since

1. I was able to mount the drives and switch TTYs on the recovery usb.
2. After installing the stock Zen binary and booting into that, I was able to do the above too.

The final issue has also seemingly just shown itself. My /run/66/log/0/current doesn't get written to, despite my verbosity being set to 4. This happens regardless of the kernel, so I don't believe it's an issue to do with that. For instance, I saw that there were only 4 lines in it while booted into my custom kernel, so I decided to reboot to see if that would fill it properly. After which, the inability to mount my 2 drives kicked in.

Edit: Forgot to add a link to my kernel config:
https://pastebin.com/7G4UwySs

My /run/66/log/0/current (verbosity 4):