There are multiple things which can cause that issue. cryptsetup package had changes for systemd 253. However we still ship 252, which doesn’t have that. Hence I reverted those changes on the cryptsetup package to match our systemd series. So yes, apply the update and see if that magically solves your issue. Take part at the discussion we have about that topic and report back your finding: Can't boot LUKS encrypted install after 2023-03-31 stable update
If someone can still boot, we call it a nag screen. Since we don’t know what the actual issue is, those community suggestions helped some of our users. As soon as there is a solution or guideline we will update the information. So far it is partly guessing. You can read my take on it to have more info about it.