Spectre: Possible to avoid "dangling node" removal when using "deepprobe" elements?

Hello! Is there any way I can tell spectre not to remove some dangling nodes in my circuit? I would like to keep some dangling nodes that I connect to "deepprobe" elements for observability purposes, as explained below.

I am trying to use deepprobe components to "alias" internal nodes in my circuit hierarchy to names that won't change depending on which views I use for the internal modules (e.g. schematic or extracted), so that I can use them later in calculator expressions and/or the waveform viewer. For example, if I simulate my DUT with only schematic views for every block, then the following node exists:

DUT.module1.submodule1.voltageA

However, if I simulate with the extracted view of submodule1, then the proper way to access that same node becomes:

DUT.module1.submodule1_voltageA

Furthermore, if I use the extracted view of the whole module1, in the netlist this node becomes:

DUT.module1_submodule1_voltageA

And so on. So my attempted solution is to use in the topmost schematic (i.e. my testbench) a modified deepprobe element with 3 CDF parameters where I can put these 3 different hierarchical node names,  and use a netlisting procedure that generates the following entries in the netlist:

MYPROBE1_1   (DUT.module1.submodule1.voltageA     my_alias_name_for_this_node)    iprobe
MYPROBE1_2   (DUT.module1.submodule1_voltageA    my_alias_name_for_this_node)    iprobe
MYPROBE1_2   (DUT.module1_submodule1_voltageA   my_alias_name_for_this_node)    iprobe

This works fine since in any given simulation only 1 of the entries will correspond to an actual existing node, so the other 2 result in "iprobe" instances with one dangling node, and are therefore removed by the simulator.

The problem is that since the deepprobes are actually connected to nothing (in the schematic I just connect them to wires with the desired alias names and terminate these to  "noConn" elements to avoid floating node warnings), upon simulation spectre detects that these nodes are dangling, removes them, and as a consequence I cannot access to these signals!

In case it's not possible to make spectre keep the dangling nodes, I guess the only alternative would be to load the dangling nodes with some dummy element, but since I have lots of these probes in my (already heavy) testbench, I would like to do this in a way that will complicate the netlist as little as possible and/or that would minimize the possibility to create convergence problems. If I add a small cap I think I will add more nodes to the circuit; if I add a small conductance I would probably want it to set this to whatever the "gmin" simulator value is set, but I don't know how to do this.

Thanks in advance for any ideas on how to best overcome this problem!

Cheers,

Jorge.