Possibility to influence the naming of NSDs in a Db2-managed pureScale installation

We run a regular cloning of a Db2 pureScale to provide a time consistent copy which is used for BI/DWH purposes.
This is done via storage features, in our case with HDS (Hitachi) Shadow Image (similar to IBMs FlashCopy).

We don't have any issues to clone the databases as long as number, size and naming(!) of the disks (NSDs) are totally equal  on source and target side.
But: As soon as we have to change s.th. on the storage layout (i. e. add one or more disks) we can quickly run into a situation where the given naming of the NSDs on soure and target differs.
In this scenario it is impossible to run a clone as this file system information (including the names of the disks) is physically stored and cannot be influenced or manipulated during cloning process.

We ask for a possibility to define the names of the NSDs we are using, for example by reserving a special name space for the NSDs of cloning-relevant Db2 filesystems.
In "native" GPFS/Storage Scale you can do this via Stanza files (as far as I know) but if GPFS is encapsulated within Db2 pureScale the given names of NSDs is just "gpfsXXnsd" where XX=1,2,3,...11,12,... I've attached a few (animated) slides to kind of visualize our problem.
Obviously stanza files are not available in a Db2-managed pureScale installation (or only used temporary during installation process). Providing those in a persistent way might be one solution for our problems. Maybe there are others/better ones...

If we had the chance to predefine the NSD names (or the name space for XX in my example) we could guarantee that subsequent additions of (Db2) disks wouldn't interfere with our cloning configuration.