Profile Types & Browse By Profile: Design Constraint - Need Workaround

I use ES Profiles for two purposes:

1. to set limits on access to features in order to maximize revenue based on subscription types, and
   
2. as a way to identify the types of members in the community --- user affinity.
   

This works well except when the ES interface may expose profile names, such as in "Browse Users". What happens is the use of Profiles to limit access to features based on subscription rates bumps against the use of profiles as a way to group user by role or affinity.

Here's an illustration where the UX is messy because I'm mixing using profiles to identify user roles but have also used profiles to meter access to features of the community. I really want users to be able to select ALL Students or ALL Teachers or ALL Administrators. Do you have a suggested short-term fix or might this be addressed in a near-term point release of 1.3? (in which case I'll just wait). In the illustration attached, the better usage would be to show just 3 profile types (Students, Teachers, Administrators) rather than have all 9 exposed which just details their subscription price/access to features.

Maybe there could be a profile tagging or profile grouping and then browse by tag or grouping?

How did Stack Ideas envision this would work?