they DO currently have that freedom - by disabling secure boot.

if the user has it enabled, the OS should assume they want it to work as intended.

was there a better way to do this? absolutely, without question. but to suggest that this situation should not cause a failure to boot is not the answer here. (that was a double negative. to rephrase: this particular combination of circumstances _absolutely should_ cause a no-boot situation.)