All I've read so far is that it cannot be done.
I have news for the unbelievers; it can be done quite easily.
I took an already working configuration for BTC mining. The scope of this thread is not to step you through all the guts of getting BAMT to mine at all but to take you from headlessly autostarting and remote reporting BTC mining to doing the same trick with LTC mining. If you need help with the basics then this thread
is a great read on the topic although it is specific to BTC mining.
Step 1: Create a cgminer.conf file. The easiest way is to launch cgminer with your preferred command line strings and then press S then W to write out the settings to a config file named and located by your choice. I put mine in the /opt/miners/cgminer directory named scrypt.conf. Easy peasy. One thing to make sure of is that you include --api-listen in the launch strings or include "api-listen" : true, in the conf file itself. This is necessary for gpumon to play nice and be able to report the relevant information. Otherwise setting up a cgminer conf file for pool failover and the appropriate settings for optimal mining are beyond the scope of this thread.
Step 2: Create a new pools file in /etc/bamt; there is already a file there but I copied it to a new one and modified it for the ltc pools I am using and named it "scryptpools", easy peasy.
Step 3: Create a new bamt.conf file in /etc/bamt; there is already one there so I copied it to btcbamt.conf and another copy to scryptbamt.conf; I'll tell you why in a bit. In your scryptbamt.conf file you need to change the pools pointer to reference the scryptpools file you created above and you need to change the cgminer opts pointer to read --config /opt/miners/cgminer/scrypt.conf (or whatever name and path is appropriate for you). Also, set the engine and memory speeds as you may have set them in your cgminer config file. Now, to switch from mining to BTC to LTC and vice versa all you have to do is copy scryptbamt.conf to bamt.conf or btcbamt.conf to bamt.conf. In this way both configs remain individually intact and the bamt.conf is overwritten as needed. A script can easily be written to do this copying for you so all you do is type a command or click an icon like "mineltcnow" or something; again, beyond the scope of this thread.
Step 4: The big kahuna to making this work. Go to the /etc/profile.d directory. Create a file called something like scryptexports.sh. The contents of this file will be simply 3 separate line that read as follows:
That is it. Save the file and then give it executable permissions for the login that will be running BAMT. To make this simple do chmod 777 scryptexports.sh. Unless you intend to reboot you can go ahead and execute this script by typing in the full file name with extension. Nothing appears to happen but if you type "env" and hit enter you should see these environment variables as now listed. These environment variables will now be set every time the machine boots.
So, finally, launch gpumon and press "D" to make sure any mining is stopped. Press "q" to exit. Copy /etc/bamt/scryptbamt.conf to /etc/bamt/bamt.conf (remember you made a backup of your BTC version in btcbamt.conf file). Launch gpumon and press "S" to start mining. Lo and behold if your configs were sound you will now be mining LTC on your preferred pool at your configured hash rate. Press "q" to exit gpumon. Point a web browser to your BAMT box from a remote machine and wala, the reporting is as expected here as well, although the graph for the hashrate will probably be miniscule unless you are pushing some serious mh/s with your rig.