I don't think things like this happen deliberately. To trigger this, you need to have a custom module without that specified indicator, and then you need to boot your previous kernel and notice that the module wasn't loaded. That are a lot of steps to get there which most people won't do.

Maybe kernel developers would get in this situation, but even then they'd probably had their system setup better for their situation (and maybe gone through that same process and thought it was part of the setup steps).