The way that any OS works (Windows, MacOS, Linux / unRaid, and the OS within the Krusader App) is that when moving files it first attempts to do a rename to move it, and if that fails then it will do a copy / replace
Basically, any move (rename) will succeed within the same mount point. This means that the file stays put on the same disk.
IE: Odds on you've passed through a mapping of /UNRAID mapped to /mnt/user
Any move within /UNRAID will result in the system simply renaming the file (because all the individual shares are all within the same mountpoint of /UNRAID). Quite normal, to be expected, and will affect every OS ever made
If you want to use Krusader to move files from one disk to another then you have to instead mount /UNRAID mapped to /mnt and then move from diskX to diskY BUT, beware that under certain circumstances (moving from diskX to /mnt/user/share or vice versa) you can corrupt the files
To be honest, the simplest and fastest way to move between shares is simply via Windows Explorer and cutting / pasting. It is just as fast as using Krusader (the files never actually traverse the network) and will respect the include / exclude settings because you are moving between different mount points (each network share is a separate mount point)