Interesting project. Did you get the connector for the front axle actuator to make the connection easier?
In my master thread on the OS about the actuator's theory of operation, I posted:
There's a 4-wire harness on the right side. It needs +12 and ground. The control signal from the TCCM goes high to command the actuator to extend its probe for 4WD, and goes low to command retraction for 2WD. There is a feedback signal that confirms to the TCCM that the actuator is working, and it sends a low for extended and a high for retracted. Upon first use, the TCCM senses the feedback signal, and if the actuator doesn't succeed in changing state when it's commanded to, the TCCM gives up, starts blinking one of the control switch LEDs, and (importantly) gives up. It won't try again until you turn the car's power off and reset the system. So if the actuator ever fails once to go to the position it's told to, the TCCM stops trying. It's not a serial data bus kind of module like the door switches or HVAC control box.
So you need to give the actuator a fused 12V on pin D, ground on pin B, High on pin A to command 4WD (and low (ground) for 2WD), and you can ignore pin C because your TCCM doesn't look for a status signal. I don't actually remember at this point if "high" in my description is +5 or +12V, but I could check sometime. If you need +5, the TCCM should be putting it out on connector C2, pin B8. I can post a picture of the connector if you don't find it in the available manuals.
http://gmtnation.com/f23/need-service-manuals-get-them-here-371/
Only fly in the ointment is that without a NP226-programmed TCCM, you're going to get NP126 behavior, which is 5% torque being sent forward all the time, increasing as the TCCM detects wheel slippage. There will be no way to command full-up 4WD behavior with that system, so your biggest benefit might only be in keeping it in 2WD mode for more predictability on variable-traction surfaces.