You raise a valid point and I have a solution in mind to try out later this week. Adding “Anonymous” as a metagroup should be a fairly simple matter. To avoid inflicting much struggle and liability on myself and others, I'll limit anon role assignments to roles that have no edit capabilities.
Would you see any advantage to also defining a “Logged In” metagroup?
Before the initial release back in May, Role Scoper did provide role assignment for the generic anon and logged user. But I wasn't happy with the implementation so I took it out. The metagroup layer is the right place to slide this in.
I think this will help Role Scoper give a friendlier first impression to some users (as well as ongoing convenience), so thanks for the feedback.
For now, you can of course get default hiding by marking each post private and then assign the “WP Subscriber”, “WP Contributor” and “WP Author” metagroup a Private Post Reader role for sections of your choice.