I don't think that kind of automatization will go a long way. It is probably simpler for the client to categorize relays in named groups -- or have some magic algorithm that cluster together relays that seem to be related to some groups.
Discussion
YES! Relay groups, like calendar group sets will be super useful
well in my mind, relays with the same/similar policies will be managed together in the same (named) grouping.
no way users can manage each relay policy individually, seems way too granular.
Yes, relay groups can be relevant. I image a "mainnet" group (the actual Twitter) of relays that sync together; clients treat them as unique subject optimizing band/cpu usage in the read/write operations. Then there will isolate (or small group for redundancy) relays that can be clustered manually by the user or with an algorithm by language, community, content typology, etc