Stopping properties from Cascading down to lower levels.

So I have been working on integrating data from our CMDB into LogicMonitor for use with alerting and observability and integration, all is going well, and I do have a work around for this, my question is basically is there a way to stop Custom Properties cascading down to instances.

For example I currently have a field called cmdb.deviceId which contains a link to our CMDB and sharedservices.dependancies which contains a list of the applications that are present on the hypervisor and Cluster, what I have found is if either of these are not present on the instance then they are cascaded for the device its self, perhaps for the deviceId that is not a bad idea, but for the applications list that is not a good idea as the reason a hypervisor may not have any sharedService data as we do not have it from the CMDB.

I can obviously work round this by setting a value in sharedservices.dependancies to "none" and overwriting it, but was just wondering if anyone else had thoughts.