That would be ideal, but it's probably more of a job for clients helping users pick their relays. I've wanted to build a relay management client for a long time that checks relay availability, specs, policy, etc (directly and via nip 66), as well as probing the relay for user access. Then, warning the user if a relay goes down or misbehaves, and migrating notes back and forth when selections change. Clients shouldn't duct-tape the network together with broken heuristics if users can't be bothered to make good relay selections.
Discussion
That's the thing, right? Users have no idea what relays they should choose, or why they might want to choose one relay over another, and there are so many relays out there that it becomes paralyzing to try and figure out which ones are "good."
Nostr.watch is cool, but I'd really like to see a relay selection tool that asks the user some basic, multiple choice questions about what they will be using the relay for, then displays a list of relays that would work for the user's intended purpose, ranking them by a few uptime and availability stats, and indicating if the relay has any restrictions for read or write access, such as paid or PoW relays.
Agreed, such a thing is desperately needed