using the `luks-device-mapping-with-options` mapped device type defined in (gnu system mapped-devices) causes grub or other bootloaders to not properly attempt to mount the encrypted drive. This is caused by the commit 39a9404 which identifies luks mapped devices by checking if the type is equal to `luks-device-mapping`, so by using a different routine that is a proxy to that one it doesn't forward it to grub in the store-crypto-devices list.
For anyone who finds this before it is fixed, you can boot your device by hitting 'c' in grub and typing these commands:
grub> insmod luks
grub> insmod luks2
grub> cryptomount (XXX)
grub> set root=(crypto)
grub> configfile (YYY)/grub/grub.cfg
Where (XXX) is the encrypted partition and (YYY) is the boot partition with the grub config, these can be found by doing `ls` command.