OK...Well, all of that didn't go so well. Finally got it to work though.
My existing online server setup works great and I didn't want to risk screwing it up by trying to make them work for both LAN and WAN at the moment...I figured I could merge them later. So I simply copied all of the server .bat and .ini files into the same folder and renamed them by adding a "LAN" prefix. Now I could tinker with these files and not have to worry about any negative fallout.
I used the Simple Lan DedicatedServer.bat as the basic template for how the new LANStartServer.bat would launch each server. So in the LANStartServer.bat file I removed the ?steamsockets option and Steam query port (27015 series of ports) section from the .bat files but kept the game port (7777 series) section and added the -ConfigSubdir option to allow separate config file folders. I maintained the port forwarding I had been using for my online servers so they could be used for the LAN servers. I went through the .bat files and made sure everything referenced the appropriate "LAN" versions of the .bat files I had copied and then fired up all 10 of the configured servers just to see what would happen.
They seemed to come up fine, so then I hopped on my gaming machine and joined each one of the LAN servers to make sure they worked. They worked without any problems.
Here is a dropbox link to the files so you can see what I did...nothing complicated at all.
https://www.dropbox.com/s/nyvdnahh7364y ... s.zip?dl=0