This is really interesting. I never figured out how to move a target and determine if there were any latency or not. It would be interesting if you can share your experiment procedure.
In order to detect something called 'radar aliasing' the sensor alternates between ranges with different pulse repetition intervals. So you get an A range and a B range. For the very first range, you get a status 6 - meaning the aliasing was not checked. With the B range, you get verification, and then get normal a status.
When your target moves, the A range will not correlate with the B range and you might get a status indicateing you might have a aliasing issue (also called wrap-around.)
I'm going to guess that you are tossing out the status 4 or 6, thinking it's an error. But if you have reason to believe the status was due to motion and not aliasing, you can accept the status simply as a warning. Both ranges were correct when you took them.