Just an opinion, it does not appear to be anything that HP would do on
purpose.
at first glance, It reminded me of tuning for weekend heavy background
processing.
Each environment is different, It would take MUCH more  analysis but..
.
1. the SAQ is hard coded at 30, which means "hogs wont fall faster" ie.
all             priorities are at the same level, if a process has a long
transaction, it will              dominate process' with a shorter
transaction without penalty.

2. you might have 'higher priority batch jobs" running in eq by the
158-202 limits
    this will most certainly add response problems to your online users,
assuming     they are in the cq, your lowest priority scheduling que is
DQ, anything in their
    might get finished some day if the system is under heavy load.  You
didnt mention your background job activity, but I would expect your online
users to get hurt if the system gets any significant background activity.

begin plug**/ My favorite HP books of all time, Robert Lund "Taming the
hp3000 vol 2" and Eugene's "Thoughts and discourses on the HP3000"
end plug**

might show this as how not to set your tuning  (this is only my opinion
and any resemblence to fact is merely coincidental)
Jim Sanders