I'm curious...what "programmability" do you think is missing in TARGET? I concede that the GUI mode is rather limited, but that was by design. The script interface however...I literally cannot conceive of anything I'd want to do that it can't.
If that was directed at me, I haven't tried T.A.R.G.E.T., and now that I've sold my Cougar + RCS setup, I can't.
Since I wasn't making much use of the Cougar's hardware logical programming capabilities in the first place, I didn't really bother to try out T.A.R.G.E.T. since it was just added unnecessary complexity. If I had a T.16000-M, MFD Cougar set, or the Warthog, though, I definitely would have installed it, since they lack the Cougar's hardware programming.
However, I did dabble a bit with the Control Manager back when I had a Fighterstick and Pro Pedals, so I am more familiar with its capabilities. It also has a neat feature to disable controllers without unplugging them (very important when I don't want games only seeing the wrong devices due to shortsighted DirectInput implementations), though if there is such a thing as a USB hub with an on/off switch for each port, that would be an adequate substitute.
Long story short, it's just a matter of familiarity, though I have heard limitations of T.A.R.G.E.T. only providing one virtual, merged controller ID to DirectInput, whereas Control Manager Scripting isn't limited that way. Has that limitation been lifted in newer versions?