There's an option to block entire instances in Connect; they'd still show up in your browser, but it's good enough if you primarily browse on mobile
All of those things can be verified before storing the password in any way, encrypted or not, and checking them would be a requisite before storing it.
While it's true that they don't have a significant impact on the hash generated, they make it significantly more difficult for anyone to guess your password. It's much easier to guess password321
than something like Or^9L%u&QQ12XxI@
. And that has nothing to do with how the password is ultimately stored.
It'll drive me crazy when I find a place to put something that makes sense, so it goes there so I don't lose it, only to forget where it made sense a week ago and end up losing it anyway