It works fine if /boot is unencrypted. You can encrypt the rest of / and it's fine.
Unencrypted boot leaves me vulnerable to a malicious actor taking my laptop, modifing grub and/or linux kernel to send and/or store my password to unlock the boot volume and then handing my laptop back and me typing in my un-lock password
Possible, but I view that threat as low
The issue I have seen is that a LOT of BIOS (at least on desktop machines) seem to just let you reset the secure boot enforcement status via the BIOS reset jumper... which defeats the point although it does raise the physical access requirement to a longer duration.