Seriously though, if you understood (from the specs or from using it) what all the wiring is about we'd not be having this conversation.
Do you use any modular synthesizers? I mean real ones, not 'I use reaktor.. presets'. Reason in flexibility is close, because you can route CV and audio between the modules.
I'm no reason fanboy, believe me. Nor was I bashing FL (which I owned and used for over a year). However in terms of wiring and fast working, reason is rather unique. I also own reaktor - yes I can route anything I want there and way more than reason does - but its not comparable to reason in terms of ease of use and workflow for writing music.
Reaktor has 'macros', modules/containers you can save and recall at any time, with GUI elements saved with the macro. Top stuff. But still its not what I'd take with me on a laptop to get ideas to paper.
Thats why I consider the combinator in reason to be genious, because it expands on the modular ideology behind reason and makes big dimensions more accessible. I.e. it doesn't become totally messy to keep track of really big setups.
You can utilize the same ideas in reason to create a sound that you have within any multi OSC synth. You use 1 OSC for the attack noise for instance, as a noise burst. The others you use one as the patch basic, a third to make it sound fatter by adding it an octave below.
What prevents you from using a whole synth for the attack phase, instead of a single OSC? Of course that takes careful programming a patch (or combination in this case), because it can get messy if you just pile up sounds without making them fit together and give each it's own job. Same problem with a normal synth patch though.
The same concept is used in hardware synths all the time, as 'combis' or 'multis' - which is nothing else, a combination of solo patches, assembled sensibly. Only reason goes a step further and lets you serially chain things up as much as in a parallel way.
Markus