I don't think that creating a new Gaia user could be a solution for this.
I do have a few solutions for you:
1) Create an admin profile that has only logs and events permissions and maybe he could see some of the objects but he won't be able to edit anything
2) I did some experiments after reading your post and I succeeded partially with some rules in the access control policy. I created "Access Role" (this is done by using Identity Awareness) and allowed it to access my Mgmt with only https/https_proxy services (the rules looks something like - source=access role ; destination=Mgmt object ; services=https/https_proxy).
Since authenticating with primary Mgmt is done with CPM/CPMI services, the user still won't be able to connect with SmartConsole to the object.
Unfortunately this didn't work for SmartEvent on my test env since it looks like the authentication with SmartConsole to SmartEvent is done with https as well and I guess that the SmartEvent uses CPM/CPMI service to further check the authentication with Mgmt machine so this restriction won't help restricting the SmartEvent itself.
3) I'm not an active directory expert but I think you can restrict people from installing specific software. If you restrict them from installing SmartConsole without admin permission.
Kind regards, Amir Senn