I'm glad that someone else finds this useful!
If you're able to do the cable shifting as pictured in the gif, then initbang is loading correctly and nothing else should break. If the cables break when you create the object then this is because initbang isn't loading correctly (looks like not you, @mil, but maybe someone else). Declaring initbang is tricky, as the object changed library designation recently. [iemguts/initbang] is the most reliable solution for Vanilla that I've found. I've given up using [try] these days, as it's quited flawed.
As for the multiple connections, I believe you are talking about "connect" mode (the larger one), rather than "shift" mode (the one pictured above)--is that correct? The limitation here is that there is no way of sensing how many connections an object has, so this has to be set by the user. It is a bit tedious, but the best I could come up with. Using keyboard input isn't a bad idea though and I'll give it some thought the next time I revisit the object.
One hypothetical solution--and something I've been calling for for years--would be an external that receives or intercepts error messages sent to the console. This would allow connector to roll on until it encountered an error, then stop. If someone wants to make such an external, I would be very happy!