Ah, more complex than I thought: "venvstacks allows you to package Python applications and all their dependencies into a portable, deterministic format, without needing to include copies of these large Python frameworks in every application archive.", and in "Caveats and Limitations" (please, all projects should have one): "does NOT support combining arbitrary virtual environments with each other".
Is there a helper to merge venv1 and venv2, or create venv2 which uses venv1 dependencies and on load both are merged?
Is there a helper to merge venv1 and venv2, or create venv2 which uses venv1 dependencies and on load both are merged?