Smarter File Operation Queueing

I am still a bit confused about what is and is not queued when it comes to file operations.

Is this intended or not?

  1. File operations from the same source disk to different destination disks are not queued. But it causes them to both thrash the source disk in a way (for me) completes slower than them being queued serially.

  2. If there is a Copy operation drive A to drive B and you do a Move operation on drive B, it will be queued, even if it has nothing to do with the files A to B. Yet if you do a Copy operation drive A to drive B and you do a Move operation on drive A, it WON'T be queued. What?

(
Kinda related, but still not clear to me:
Copy Queue: not "Moving" instantly (bypass queue) within the same drive - #14 by Georgios
)

Thank you for your attention,
Trev

The automatic copy queue rules are documented here:

There's also a scripting event which allows you to change them if you want something different.