So while it is fixed for new ISOs, I didn’t want to reinstall my system. Basically what I did, from the (initramfs) prompt, I booted manually
cryptSetup luksOpen /dev/nvme0n1p2 luks-<the uuid>`
Make sure to adjust the /dev partition to your drive. And more importantly: make sure the luks- you name it matches up with what your crypttab says your root drive should be! Then boot through (exec run-init or something)
Once booted up, put the Calamares config [1] neon now uses into /usr/share/initramfs-tools/hooks/
Then regenerate your initramfs sudo update-initramfs -u. Pay attention that there is no cryptsetup: WARNING: target ... is not found in /etc/crypttab. If there is, you probably mistyped your luks- above or it doesn’t match up or an encrypted partition you have wasn’t set up properly.
If there are no warnings of the sort, try rebooting. (This message is proudly presented to you by a working neon installed with three weeks old ISO image fixed just this morning)
[1] calamares/src/modules/initramfscfg/encrypt_hook at calamares · calamares/calamares · GitHub