I've always personally felt many of Nintendo's games specifically limit the art in the service of gameplay where as many other companies are "art first" companies. Zelda in particular aims at making worlds free of clutter and trying to make nearly everything interactive. Compared to most games where 99% of all doors are not openable, 99% of all plants are not manipulable, 99% of all rocks, pots, etc are not movable. If you let the artists fill up the world you get Uncharted, which while it might be a great game in it's own way, it's also massively static compared to nearly any Zelda game. If they let the artists fill up Zelda to be as art drivin as Uncharted it would no longer feel like Zelda because Zelda is about gameplay, Uncharted is about art.
(And how much of that is a problem with just OpenGL vs. how much does it apply to DirectX as well?)
http://channel9.msdn.com/Events/Build/2014/3-564
youtube dupe: http://www.youtube.com/watch?v=m0QkjKGZQzI
That blog post should help you clarify the difference. I think the primary problem it that OpenGL and DirectX handle changes in pipeline state very poorly.
While working on this game, I got some code that a colleague wrote for another product to pre-generate all the GPU commands offline, so things could be drawn with 0% CPU overhead. But once I'd merged it all in and got it working, the thing was actually slower! No good sending them all to the GPU and letting it deal with them, it turned out. It was faster to have the CPU carefully check each state setting and not bother the GPU with the redundant ones.
(Sort-of disclaimer: Wii developers never got tools as good as the ones for the PS3 or Xbox360. In particular, there was very little visibility into the GPU's working, just some poorly-documented performance counters, and a Javascript tool that would estimate a per-vertex cycle count for a given set of vertex attributes. So it's possible I just got something wrong. And sadly I can't claim to be the sharpest tool in the box.)
Still, great analysis.