its not the engine per se, but the design decisions that resulted in various key features that allow other engine modders to gloat about so easily.

mh, While I've no doubt that directq reaches 99% gpu usage, I feel I must point out that you could push the entire map to the gpu in a single vbo without any culling and still get 99% gpu usage, yet get a third of the framerate. I'm kinda distrurbed that DP is actually reaching even 80%, I can only assume that's the sky renering.
Ace12GA, The ideal of optimising is not getting 10 million fps, but optimising the cases that really need to run fast. In DP's case, this is rtlights. For every other engine, demos like bigass1/overkill etc are a higher priority - worst case scenareos that will actually happen when playing competitively.
For the people who's machines are simply not powerful enough to run rtlights, and are still underpowered for other things too (say, cheap intel gpus or laptops), any performance from DP just isn't there - it really isn't optimsed for it. People 'forced' to use DP just to run specific mods when some other engine would get twice the framerate are understandably going to be resentful of that.
DP just isn't competitive against other clients. This is most comic with DP's QuakeWorld protocol support - a server where you have people playing with _stable_ 320+ fps, and a DP client joins with default settings... rtdlights etc... They get owned so fast.

Like that mod on here a while ago that used dpm+framegroup files. If it had used iqm instead of dpm, then it would not have needed the separate framegroup files and would supposedly have been able to run on DirectQ, RMQE, FTE, and presumably soon QuakeForge in addition to DP. However, it uses an older dp-specific format and thus always has half the framerate of these other engines. Now, I'll agree that there's a tools issue here, but don't expect everyone to really aprechiate that.

Now, I'll admit that I don't know if it uses any qc extensions too or not. Considering it said 'DP-only', I didn't bother to check.
Everything is a compomise between performance, features, usability, code size, binary size, readability/maintainability, etc. DP just has different priorities is all.
But then, differences in priorities is what drives diversity, and diversity is good in the long run especially with all the engines that support similar feature sets.
.