It's an old problem within software itself and not really addressed until the individual puts their foot down and says, "This. This is the medium, these are the restrictions, this is the way I structure everything." At that point it's possible to define perfect software, but we're too fickle to really get there.
Reason + Cubase linked together was a lot of fun :)
That's spectacularly wrong. The core workflows (sequencing, editing audio, mixing, etc) are similar in every DAW because that's their inherent nature, nor because they're somehow imposed upon users.
The only major different paradigm was Live, which, as it name implies, offered a "live clip launching" way of interaction. But that's not about "imposing a strict workflow" it's about supporting a different use case or not. In other words, it's like there were editors for programming, and someone went and make an editor optimized for live coding. And even that, is offered in several DAWs, including BitWig, FL Studio, and even Logic.
The core workflow itself (which involves sequencing, editing audio, mixing, etc) has 100s of ways it can be mixed/matched/customize/performed differently within the same DAW.
This is amazingly wrong. DAWs are notorious for imposing a specific workflow, and users will select a DAW specifically for some new workflow it has produced. For example, Ableton rose to prominence largely due to its unusual alternative workflow option (the grid) which made it popular on the DJ scene. Other DAWs have workflows and tools which make them popular with composers (Cubase for example) or tinkerers (Bitwig, Reason, etc.).