Hello Mr. Jammer,
I'm not aware of anyone having done the kind of work you propose, but it should be possible. I'm curious about your scenario, though. Do you have an existing membership database you need to re-use? Are you designing a solution that needs to support billions of users?
Usually, for those kinds of scenarios, we expect folks to create their own MembershipProvider and RoleProvider classes (which, incidentally, are what WebSecurity calls under the covers). This is also likely to be much more performant under high loads.
If you think there's a scenario that's missing, let me know and I can put in a good word for getting a bug fix in.
Thanks,
Clay