We use layouts but that has issues of its own. The technical view is barely usable and tends to break when using blocks (things disappearing, random lines coming out of the origin, part outlines coming out as hidden lines…).
If you’re doing bent sheet metal parts, hopefully you’re doing something very special because you might be spending a lot of time manually doing flat patterns that account for bend deduction…
It’s not all rainbows and unicorns with mechanical CAD software either. Constraining everything tends to be extremely time consuming, especially when you can get there quickly in Rhino. Also, changes will often end up needing a rework in the parametric tree which negates all the time you spent setting the constraints in the first place… But yes having more info in the model is super handy for a lot of stuff, most of this stuff comes from Vault though. Generating BOMs, being able to know which assemblies use a specific parts, being able to print all the drawings relating to an assembly in about 4 mouse clicks, etc. Rhino is very good at giving you the tools to make awesome geometry, it’s not very good at everything around it.
GH is its own beast and it’s one of the reason we keep Rhino around. What’s in the Zaha Hadid Morpheus case study yes is something like a million unique parts. But you have to keep in mind that its a few dozen types of unique family of parts, the bulk of it is variations within those families. So you spend a lot of time to setup your drawing nice and tidy and then when you feed it all those variations, the drawings mostly come out fine. The other way to deal with these is to make a clean typical drawing and provide tables for all the variations.