Probably not. The changes for full-disk encryption (FDE), which is currently used, to work in TWRP for 12 are for devices with TWRP built from 12L sources. Our TWRP builds aren't built from 12L sources. Tried getting builds built from 12L sources long ago, but failed on my first try and didn't try any further.
With Android 13/20.0, support for FDE has been dropped, so there's only support for file-based encryption (FBE) that isn't optional and needs to be enabled for everyone, which I'll do, anyway. TWRP is completely lacking in any working FBE support, got various problems with it when trying it months ago, and in that way, it's obsolete. When moving to 20.0, we'll have to start using LIneage recovery, but there's some problems with ADB, and especially ADB sideload, with it that I'm struggling with. I guess TWRP from 12.1 sources if I got it booting at all would have similar problems, anyway.
I'd guess that problem is probably specific to your router (and I also guess firmware-independent). No WPA3 router to test with here, so can't do any testing.
I seem to remember stuff about these devices and other devices not connecting to mixed WPA2/WPA3-SAE networks, but I think also only with certain routers, hmmmm...
That's natural. A device can't be aware that a network is WPA3 if it doesn't support it. Your OnePlus 7T would definitely support WPA3, so your network shows up as supporting WPA3. So, I suppose with this,
@Tamhvm's would more than likely be a router-specific problem.
Never had such a problem, totally unreproducible, and no ideas. Why not update to the latest build by the way?
Go to Advanced -> Copy Log in TWRP, and use that function to get a log after trying to install the build, and send it here.
That error is completely undescriptive and useless. A full log will contain actually useful details.