Doing a bit of research on the RDNA site on Parmatic, and I ran across this:

*** After loading and selecting your AM figure, click one of the base shaders. This will load the shaders, call the parmatic updater to create the dials, then invokes the Parameter Dials pz2 file to sort and organize the dials into groups. (The Parmatic Updater Python script has no access to groups or dial order - so that's handled by loading the pz2.)

• The presets are pz2 files with specific values for the dials. The Parmatic Updater is sitting around in memory waiting for dial changes. Upon loading a preset, the dials get new values, and the updater notices and copies these values into the shader nodes.**

So, hang on (looking at the underlined bit): does this mean that the Parmatic Updater script must be run at least once per Poser session in order for the dials to work? So, in order for the non-developer / product user to get any benefit from the dials, they would have to run Parmatic themselves first, otherwise the dials don't work?

Back to reading...

Edit: Geez, it says it right there in the readme:
These scripts will scan your materials in a figure or prop,  create actor parameters for them, then update ALL the  materials as you adjust the parameters IN REAL TIME!

So, the script does the updating of the material node channel values. Well, that makes sense. But it kinda takes this concept out of the realm of something distributable, for it would mean the end-user will have to get a copy of and install Parmatic for themselves for the dials to work.

Mind you, I love this tool! But then, I'm a geek.

Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2

Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand] 

Metaphor of Chooks