rename/move/copy is NOT appropriate to move a lot of files, for a lot of users...because it doesn't move associated files! (log, cue, pdf/jpg booklets, etc)
It moves what you tell it to move, and any associated sidecar files
that MC itself created.
I think that is appropriate. It would piss me off to no end if it had some kind of magic secret logic where it decided based on filename matching if it should move files that it never created, I'd never imported, and which weren't selected when I did the Move operation. That behavior would be completely broken, as far as I'm concerned.
I get that it would be convenient in some cases, and I wouldn't be opposed to an option to also move possibly related sidecar files. However, bear in mind that this could also cause issues. Imagine if you move files out of a "catch all" directory (that's how I import most of my files -- from a catch all M:\incoming\ folder) which contains large numbers of completely unrelated files all dumped in the root directory. So, it would have to be able to decide, somehow, if a particular LOG file or PDF "belongs" to a particular set of files, or another one. Also, what if you don't move them all, or you split an "album" up into pieces (which it'll do depending on your rename rules)?
You CAN solve this problem now. Simply import those files, and when you do Rename, Move, and Copy, select them all (including the auxiliary files) and do the operation on all of them.
That's what I do, and it works fine. You do need to tag the sidecars like you do the sources, but this isn't a huge issue in most cases, if you have a well-designed view to use.