Possibly long story, long ...
Some of the nodes in the Data360 node library are built using Composite nodes. Similarly, you may have created custom library nodes that utilize Composite nodes. When you drag a library node onto the canvas you create an instance of the library node. The library nodes that are based on Composite nodes can be opened, as usual. The contained nodes will then be displayed similar to the following:
These 'shadow' nodes - probably more correctly referred to a s'virtual nodes' - are inherited from the Composite library node. The 'down-arrow' on the virtual nodes indicates they have not been modified from the configuration that was inherited from the parent library node. Similarly, the connections between virtual nodes are shown as dotted lines rather than solid lines.
In the above screenshot there are some nodes that are enabled (e.g. the Switch node) and others that are disabled - the latter are displayed with their icon 'washed-out'. Similarly, disabled connections are shown washed-out. Typically nodes are disabled due to the configuration settings of the properties on the parent Composite node.
You can modify the configuration of virtual nodes. This is signified by changing the badge on the node [see the Transform (Superseded node below) ]:
If required you can disable virtual nodes or add in new nodes (which are shown as normal, together with their connections):
Analyze does not allow you to delete a virtual node within an instance of a parent composite library node. The only option currently available to you would be to disable the node.
I hope that helps clarify the current situation.