Well, I did see that manual page. Unfortunately, it's still not clear for me how to program my own queuing behavior.
The described behavior should be mapped by the queuing algorithm. It should be obvious that reading and writing on the same hard disk at the same time is not a good idea.
It would be helpful to be able to define own rules. Or why it is not at least possible to define only one queue where everything goes in as a quick fix.
IMHO, it would still be a good feature for the queue to honor C -> D and D -> E concurrent copy methods. Maybe a feature you could implement in later versions?