The more I mess with this, the more it looks like some kind of strange quirk with that particular user account and profile.

The user account was once an administrator of that machine, and was later removed from the administrator's group. Perhaps that is the reason it's behaving that way.