Ahh right, fair enough.
It seems like you would have to have a way of deploying the Python scripts to each PC, either via a network or over a version control system like Perforce, right?
I will say that MaxPlus is notoriously short on features and for most solutions will only get you 80% of the way there.
Our tools deployment works as follows:
A Python installer script adds custom paths to Additional Macros, Additional Startup Scripts and to the 3rd Party Plugins in 3dsmax.ini and Plugin.UserSettings.ini. This is run once when installing the tools.
All our Macros are stored in the Macros path, all api/functionality scripts are stored in the 3rd Party Plugins path and there is one startup script that does all our setup.
The main point of interest for this thread is our deployment of our Python tools; they follow the basic steps above, Python module > Python “MacroScript” importing and executing the Python Module > MacroScript importing the Python MacroScript via Maxscript.
The key thing is the Python MacroScripts are procedurally generated on startup, removing redundant ones and generating new ones as required.
We then have a menu generation script that creates a menu procedurally based on the folder structure of the MacroScripts path. This uses maxscripts MenuMan, which can be accessed via pymxs.runtime.menuman if you are on >= Max 2017 , MaxScript if < 2017.
The minimum I think you could do here is to modify your batch script to update the 3dsmax.ini and the Plugin.UserSettings.ini to include a path to your Macros and Startup Scripts, stored where ever you are storing your Python scripts, and write a startup script to generate procedural MacrosScripts and Menu.
That is the best I can offer as I doubt MaxPlus will get you where you want to go.
This might be a helpful thread to read as it touches some of the same topics: