Well… in my eyes there is not really a need for any kind of configuration:
The 8K-X has an additional USB-2.0-power supply 
… as the 5K+ had/has 
… and the 5K+ shuts down completely when the power supply’s socket is switched off 
=> What is so difficult about using that same logic for the 8K-X…?!?

IMHO the logic is quite simple:
- USB-2.0-power supply connected and power ON => HMD either ON or maximum STANDBY via HMD-button
- USB-2.0-power supply not connected OR power OFF OR PC-power OFF/shut down => HMD OFF
Might be I’ve forgotten something
- but in general, I don’t see any reason why Pimax can’t handle it similar to the 5K+. They just have to check whether the USB-2.0-cable gets power or not, especially if someone has connected it to a wall charger with socket switch. Should nothing be easier than that.
Just a bit a pity, that a more modern HMD launched two years later falls back on that point…
Furthermore, I noticed yesterday evening, that when putting my 8K-X to real stand-by via the HMD’s button, I always get a hardware error event #144:

Even more curious, that event occurs only ONCE per Windows session, between boot/Windows LogOn and shutdown/Windows LogOff. Means: I can relaunch the 8K-X and put it back asleep multiple times during one and the same single Windows session, but that error #144 occurs only the first time.
Fortunately nothing more happens, everything works and runs, standard flat gaming as well as VR, no crashes, no BSOD or the like.
However, a bit curious, annoying and unusual, too.
I will double-check that by updating my NVidia graphics card drivers - but together with that USB-2.0-issue, that sounds rather uncommon to me…
I’ll keep monitoring and probably open a new issue topic on that so @pimax doesn’t have to read through all this topic here 
EDIT:
NVidia drivers updated, played an hour Elite Dangerous in VR.
Pressed the HMD’s power-off/-standby button - and once again hardware event 144 exactly at this point in time (I did a reboot after driver update):
So, this problem isn’t related to the graphics card driver.
Can anyone reproduce and confirm? => Reliability Monitor
Opening a separate thread for this one; posted it here just for the sake of completeness.