Hrm. So you've unwrapped entire mechs to textures and then split the model apart so you can have piecewise mechs where for some odd reason you want all the individual pieces to use the same texture file?
The answer from a proper pipeline standpoint is to allow each piece to use its own texture file- as long as you've loaded all the textures into Unity, it shouldn't actually chew up more VRAM to have multiple textures represented in multiple pieces of your mech. You may want to even split out and re-unwrap your mechs as separate pieces that can use separate texture files. This will make everything more modular and less headache-y.
If you really want to stick with compositing multiple parts of multiple textures into a single image, your best bet would be writing a shader that takes multiple textures and a grayscale mask image delineating which pieces of the final uv space to fill from which source image.
If even that would be a stretch, you may be able to somehow composite multiple Decal shaders, each with a texture that is transparent save for the part of the map you need, but I'm not sure offhand if Unity lets you stack render passes like that.
If you want to get REALLY pathological... I suppose you could (on a Pro license) stack up multiple simple full-viewport-sized planes each with an unlit transparent material and a component texture similar to the previous idea, render that to texture via a script, and plug the render result in as your final model texture.