I'd probably start by booting with nomodeset and in verbose mode and hope you can at least get some debug output. If you have Plymouth, obviously disable that. Anything that can give you some logs and possibly a crash dump to figure out what it's doing when it dies.

It might also be worth running a quick memtest86+ just to rule this out, you may have dead RAM and memory aligns in a fatal way there with newer kernels and there's nothing wrong with the kernel itself. There's an open Arch bug report for 6.6.2 that suggests memory corruption as well, so it's definitely worth a shot.

If you have another device, you could also have it send the logs there over the network, I think it can just send them out over UDP so it's likely there's an Android or iOS app that could receive the logs.

If this is Arch, bisecting might not be as hard as you think. Compiling kernels is not as horrible as it sounds, even on other distros. For the most part it's more or less the same configure+make steps especially if you reuse the config of the currently running kernel, which it can use pretty much automatically.

I mean, no, but this probably isn't the way you want to go about dealing with it.

If you know how to build and install your own kernel out of git, and how to run a git bisect, you could go back and identify the exact commit to the kernel that introduced your problem, which would probably do a lot to help accelerate getting the problem fixed.

The new kernel update fucked up my wifi which in turn fucked up KDE and I couldn't even use my terminal. Wish it wasn't rushed, and just left alone until after new years tbh