I don't think it is rawmove that causes this but I specifically asked GoogleFrog to "fix" movement when you are trying to move units ontop of buildings, features and unpathable terrain.
What used to happen was that units would just stop before they reached the edge of the building or the terrain and I wanted them to move at least to the edge of the building or maybe even to the other side of the building, if that was the closest pathable point near the unpathable move order.
Worse yet, if units got their move orders on unpathable features they would also stop and this basically made autokiting units completely stop if their automatic move order were on a wreck even if that wreck is tiny and there is no other wrecks besides it.
The fix that GoogleFrog implemented, might be responsible for this but I'm not sure. You would have to ask GoogleFrog.
Rawmove should only be triggered when the path to the destination is clear of anything that is unpathable, and should not be responsible for these types of issues.
Rawmove is mostly a big improvement to pathfinding and unit responsiveness.