By using Krusader, you are effectively bypassing the "system", resulting in this behaviour
The way that every OS in existence operates on a move is that first the file / folder is attempted to be renamed to the new location. Only if it fails does the copy / delete process (physical move) take place.
Because Krusader is working from the single mount point (/mnt/), the rename will always succeed, resulting in files being location in apparent violation of the rules.
Options to avoid this is once 6.10-rc3 is released to install a File Manager plugin at the same time, or 2 do file operations via Windows and move between the shares, or map the shares to Krusader individually and move between those mounts