Naudiz I think besides not knowing the actual name of Lockdown Mode I didn't say anything particularly wrong, or did I?
For example, you cited a โ72โ hours timer, implied that you can't use your primary unlock method when fingerprint unlock is available, said that your device is in a more secure state when fingerprint unlock is disabled (it's vague but I took it as a hint that you might be thinking about BFU state, in which case you're wrong), and other incorrect ideas I detected in your post. (You didn't do anything bad, I just thought my tutorial would be particularly helpful to you due to this.)
Naudiz Providing the wrong fingerprint 5 times in a row locks the screen to the primary unlock method
(This is an intentional GrapheneOS feature, by the way.)
Naudiz Anyways, last night I locked the phone by using the wrong fingerprint 5 times and was able to handle the alarm just fine this morning. Maybe this is the way to go for me from now on - it's a bit clunkier than just pressing a button in the power menu, but if the alarm popup is more reliable this way it's worth it.
AcclaimSublevel19 activating lockdown mode achieves the same then
Lockdown Mode seems to do much more than disabling secondary unlock methods. It also seems to block overlays in the lock screen (hence why the alarm rings but doesn't appear) and block the USB-C port (which GrapheneOS seems to have recently upgraded to use the same hardware-level blocking as their USB-C port control feature), and maybe more.