There actually were operating systems which have the exact problem you describe. I say were because although in fact like any software operating systems don't vanish, they're so unpopular today that they're irrelevant.
Amiga is an example. The Amiga OS doesn't have that clean Unix-style border between userspace and kernel, so even on a "modern" PowerPC AmigaOS you can (and people do) write a user program that will say I must not be interrupted right now, I will disable interrupts, and do my thing and then I'll turn them back on and re-enable the operating system.
When Linux was young it was a resolutely uni-processor operating system. Linus wasn't interested in fancy "server" hardware, so, why not. But because it has that Unix separation, when SMP was added they did the thing most Unixes did, they added a Big Lock, software which worked correctly before still worked because as far as it knows nothing changed, the radically new multi-processor world it is actually living it seems exactly like the previous world thanks to the Big Lock (getting rid of the Big Lock took many years of effort from there, but introducing the multi-processor feature was in this sense easy)
Amiga couldn't (and even today can't) do that. Being able to turn off all interrupts and suspend the operating system is a feature, but, what does that feature mean if there are multiple processors? It becomes nonsense.
Hyrum's Law is an observation about how users of your software behave, but it is not a law requiring you to give up and stop innovating because any changes would break people, it's a caution to design things that aren't so fragile, and a reminder that whenever you step over that line you'll cause pain.
If they had the guts AmigaOS 4.0, many years ago, should have dropped the "disable interrupts" features. There would have been wailing and screaming, as with Firefox getting rid of legacy "reach inside the guts and do what you want" functionality but the wailing and screaming doesn't last forever and it sets you up to actually innovate and not remain stuck offering a 32-bit uni-processor OS decades later even though your flagship hardware has a 64-bit multi-core CPU.
There actually were operating systems which have the exact problem you describe. I say were because although in fact like any software operating systems don't vanish, they're so unpopular today that they're irrelevant.
Amiga is an example. The Amiga OS doesn't have that clean Unix-style border between userspace and kernel, so even on a "modern" PowerPC AmigaOS you can (and people do) write a user program that will say I must not be interrupted right now, I will disable interrupts, and do my thing and then I'll turn them back on and re-enable the operating system.
When Linux was young it was a resolutely uni-processor operating system. Linus wasn't interested in fancy "server" hardware, so, why not. But because it has that Unix separation, when SMP was added they did the thing most Unixes did, they added a Big Lock, software which worked correctly before still worked because as far as it knows nothing changed, the radically new multi-processor world it is actually living it seems exactly like the previous world thanks to the Big Lock (getting rid of the Big Lock took many years of effort from there, but introducing the multi-processor feature was in this sense easy)
Amiga couldn't (and even today can't) do that. Being able to turn off all interrupts and suspend the operating system is a feature, but, what does that feature mean if there are multiple processors? It becomes nonsense.
Hyrum's Law is an observation about how users of your software behave, but it is not a law requiring you to give up and stop innovating because any changes would break people, it's a caution to design things that aren't so fragile, and a reminder that whenever you step over that line you'll cause pain.
If they had the guts AmigaOS 4.0, many years ago, should have dropped the "disable interrupts" features. There would have been wailing and screaming, as with Firefox getting rid of legacy "reach inside the guts and do what you want" functionality but the wailing and screaming doesn't last forever and it sets you up to actually innovate and not remain stuck offering a 32-bit uni-processor OS decades later even though your flagship hardware has a 64-bit multi-core CPU.