There’s another nasty one I encountered where power loss on a mac mini with 4 external drives connected made one drive refuse to mount on that machine. All recommendations online were to nuke the OS and/or drive to get it to mount there again. It would mount on other machines fine. There’s some cache/index file buried (I think related to spotlight) that got corrupted. Nuked that file, drive mounted instantly again.
These types of things should stand as big massive red flashing warnings with all these locked down systems - as you point out, in certain situations on iOS you’re just stuffed.
The worst is that if you look at Console.app and stream error logs from the system processes, there's hundreds of error logs per minute being dumped out on a brand new system with nothing installed on it yet, including and especially from spotlight. There's bugs all over the place that some engineer at Apple thought enough to emit a log for, and the result is they just ship with the errors anyway. They only seem to care about 100% reproducible bugs, and even then they sometimes ship with them anyway. They don't seem to care about all these little unobservable issues that "only" log errors, even though 9 times out of 10, when a bug does become a reproducible/observable issue, there was an error log that was warning you about it the whole time.
If I took over Apple's software engineering, I would tell every engineer "None of you are working on features until a stock OS install has zero error/warning logs. No exceptions. Contribute to fixes or use your vacation time, but nobody touches anything until we get it all fixed. Then once that's done, nobody's allowed to work on features while there are open bugs in their backlog. No exceptions."