Do the same with stash commits. Store them as regular commits flagged as broken and hide them when viewing history.
Hell, do the same for most history-modifying operations. The ability to flag intermediate commits as "unimportant" would let you be able to keep a clean history without rewriting it.
Maybe you want to share your work with others even though it's still in a rough state.
Maybe you have automated tests in your CI process and you want to try those tests on your side-branch.
The point is you might want to wrap workflow around your stuff, even if it's experimental and broken.
Git doesn't make these choices for you. You get to make them.
I find that making a work-in-progress commit, and then resetting later ends up saving a lot of hassle overall. Having support for this beyond aliases (including putting that commit in a new branch) would be nice.