I think that someone may have been me? Hehe. Funny
Anyway, as I understand it, setting the priority has more to do with needlessly slowing down your other traffic with little gain to the traffic tied to the QoS rule. Think of it this way. You go to a school with 3 bullies. Everyday you aren't allowed in the cafeteria until they get there to get first dibs on the food. As soon as the class bell rings, the bullies walk to the cafeteria doors to get their lunch, but since they get out of class at the same time, there is nothing there to tell them which bully goes in first, so they struggle a bit, taking up time. Not only does this slow down the bullies, but having the other students wait OUTSIDE the cafeteria before they get there doesn't allow the bullies to get in any faster.
In this way, having your QOS rules set to low has too effects. First it starves the rest of the traffic on the network needlessly, like the students, in a way that doesn't give the priority traffic(bullies) any advantages. And two, having the priority rules too close together, doesn't properly manage the traffic when it approaches the bottleneck (cafeteria door).
This opinion is based on testing and understanding of how QoS works on other networks, but to be honest, since its proprietary, I don't fully understand how Dlink does it, so I could be wrong. Hope that helps though.