It’s not unrelated, as I’m talking about functionality that is provided for non-automatic interaction via the qvm-console-dispvm program, which spawns an unnamed disposable from the default-mgmt-dvm DVM template, which is what this topic is about; if you don’t have an answer for me, why even reply?
In any case, your understanding is at least partially wrong, as in multiple places of the documentation qvm-console-dispvm is explicitly noted as a tool to troubleshoot different issues with qubes, so even though the default-mgmt-dvm is classified as internal in the Qube Manager, QubesOS still provides for an explicit user-exposed way to utilize it (non-internally).