SAP BTP IS - Access Policies to restrict monitoring or object details?

[xavisanse]

Hi all, 
I've been seeing the capabilities of Access Policies in Integration Suite and that's clear. I've done a PoC and worked as intended. But... as intended is not enough.

I want to isolate not just the artifacts at  design time or just the change of traceability of deployed iflows when someone is operating the iPaaS. I want to fully isolate / restrict the objects. So If i have a pattern in policies that grants access to objects with the pattern 'AAA' the users that hasn't this, should not be able to:
- see that objects at design time (or at least the name of the objects in the corresponding list, but without access to the detail).
- Not able to monitor them. Now you can see them at monitoring tiles, even see the log. 

As explained in Package-Level Access Policy and in Artifact-Level Access Policy looks like this is the intended flow.  So what I'm trying to do is out of scope atm.

So, my point is, if i have a TeamAAA that has to monitors JUST the integrations with 'AAA' pattern how can I achieve it?

Exists the option to avoid the access to the object details or to exclude absolutely an iflow from monitoring? 

I want (wish 🙏 ) to be able to isolate them directly from SAP BTP IS. I've checked the roadmap and didn't see anything.