It's not possible without some changes. Setting for showing / hiding hidden is global, and not a policy, thus if we add a 'hide', you won't get access to show it again unless you log in to admin interface (as you should for getting access to features like this, specifically meant for administration of site and content).
I would use object states for hiding objects. Though you need to edit templates if you want to mark object with hidden state as grey for editors. Then you could set policies so that anonymous users can't read hidden objects but editor group are still able to see them.
You can create workflow for state update. There is AvailableOperationList[]=content_updateobjectstate setting in workflow.ini which enables trigger for state change.