Watch out! On Solaris you will eventually run out of file descriptors (c.f. ulimit command) and the adaptermonitor process will fail. At some limit of adapters (100 to 150?) you will overrun the operating system’s ability to track all the processes created. Setting your ulimit to be unlimited will help, and custom modifications can increase the total limit even more (i know that Peter Strimbu [V.P. of Integrations at Statera] has worked to modify the adaptermonitor script to increase the limit on Solaris machines).
Your options on 4.1.1 are very limited to actually modify the adapters without using the adapter_config. You can (not recommended) modify (not recommended) the adapters.cfg (not recommended) file directly, or you could (also not recommended) configure some adapters on a different machine and then merge (not recommended) the adapters.cfg file to have your modifications take effect.
To get your adapter_config tool to launch faster, you can remove unused adapters config files from the etc/adapters directory and the total load time will be reduced. I am not recommending this, but you might experiment with temporarily removing all the config files except the one for the adapter you are going to modify, launch the tool (only adapters of your remaining type will show up), make your modifications, shut the tool down, and then replace the config files.
I believe that wM is working on a remote-able adapter_config tool for an upcoming release, or, you could hire me to write one for you if you want (grin)!