Oh, one other thing I've noticed with BOINC 5.4.9 is that the values in the To Competion column seem to be considerably more accurate that before. That means you can tighten up your Connect to Server value. I can't see much if any reason to go beyond 2.0-3.0 for this under normal circumstances. For me, I see this as the best improvement in 5.4.9.
As for "managing" your WUs, I've seen some discussion about that and I've tried some experimenting. With 5.4.9, I don't see that it really gains you that much. Typically, you will want to crunch the WU that has the closest due date first. Given how 5.4.9 will automatically switch to "older" WUs, you have to leave that WU suspended to prevent that. There you then risk running out of work or crunching on a new WU that you got because you had no WU to run. Besides, how practical can it be to try to managing WUs if you have multiple devices?
5.4 has a duration correction factor that is used to calculate more accurate result durations. This affects how much work a host will be sent as well as the estimate used by the CPU scheduer.
If the projects are reasonably accurate in their estimates of the work to be done on a result (some of the Alpha projects are very bad about this) there should be no reason to actively manage your qork queue.