The crashes are being caused by syntax errors in the commands. And I can 99.9% guarantee they are my fault for trying to manually edit them to remove sections which seemed extraneous to what I was trying to do. (You did warn not to manual edit unless you knew what you were doing...thought I had followed things correctly, but apparently not.)
I think you have something here, and someone agrees because I saw it recommended in several different spots...I'm just having trouble grasping the syntax. I can get it to do somethings, but not others along with getting some unexpected results. I just set up a stack that compares the values of a signal on a specific color wire to a constant. It does this twice, once for a signal on each wire color. The combinator output is connected to a pair of lamps, one for each comparison. The actual comparisons seem to work, but the "second" output overrides the 1st so even when both conditions are true, I only get one output signal. I'm pretty sure this is just another "I'm using it wrong" situation...in all honesty, the final configuration would be one more step to compare the results of the 1st 2 steps. Trying to have one combinator do 2 separate thing was never what I had intended to try and do with it.
Getting back to just needing to learn the syntax you've used...it would look like the test scenario I've been trying to set up should be able to be done on one line the way I'm reading the available syntax options, but so far haven't gotten it to work that way. (This is actually where I have been manually making edits and crashing things.) Even on mulitple lines, having it all in one combinator instead of multiples, and the additional functions you've provided like being able to look at signals from specific wires is a huge improvement from vanilla though and I'll take it.