Terry,
What you saying makes no sense.
When an axis is rotary and is set to rollover on 360° then it can move 2 ways:
1.) Shorter path
2.) Longer path
Because G1 does not define which way to move, not like G2/G3 which defines CW or CCW therefor the control has to select one of the ways, because it is simply undefined.
So, moving "as it is programmed" makes no sense at all, because it is not programmed (cannot be programmed) with the G0 or G1 which way to move.
Rotary axis now works the same way as in Mach3. (If that makes any sense?)
When the path feedrate is calculated then it is calculated on XYZ if there is XYZA axesprogrammed with the A being rotary, then the A axis only follows the XYZ as fast as it's acceleration and velocity allowing it to do so.
In this case the A axis will only limit the XYZ movement if it's velocity and/or acceleration is not fast enough to let the XYZ move with the programmed feedrate.
I do not know what "rotary axis radius comp" is. What g-code is that? G96? That is not supported yet.