Separate Pull Distribution Point Throttling from Agent Throttling
If a Pull Distribution Point is throttled, this affects the remote site system from a client perspective, so its client downloads are throttled as well (even though those downloads may essentially come from itself).
Throttled download jobs, as the system is functioning as a Pull DP, should be separated from throttled download jobs as the system is functioning as a client/agent. I'm not sure how this can be accomplished; it may have something more to do with BITS than something internal to ConfigMgr, but it would be welcome.
