Eudyptula Not accurate:
Android has extensive testing for the defaults but most developer options are essentially untested for production use and often cause issues. Many sound like they may be things you may want etc but are actually a bad idea and that's often why they're still only in developer options.
Android's animation speed configuration is still only available in developer options because it's known to be very buggy. They added the toggle for disabling animations as a whole outside of developer options, via accessibility which is meant to be stable now but the default is the most robust.
We recommend avoiding using ADB and developer options as a whole on a production device. Users who use them consistently end up doing things like disabling core OS components and making changes which ends up causing problems.
Enabling developer options requires authentication with the lock method so having an unlocked device isn't enough to enable developer options and then enable ADB. Good reason to keep developer options disabled since someone who gets temporary access can't set up ADB, etc
While I appreciate your individual position and view, it is not a one size fits all approach. It also doesn't fit the ethos of the OS and the community. So while you say "no, Developer Options is dangerous and bad so stay away from it and don't touch anything" isn't useful, I'd say based on our experience providing support and finding in the end the issue was a result of people using them without understanding what the underlying consequences and changes are it is very useful.
That being said we/I concede that how people use and operate their devices is of course and without debate their prerogative, it remains ours to determine the projects/moderation teams position to advise against it, and that discussion and promotion of using them is best placed elsewhere.