well I guess that is probably the end of the line for this investigation then
Strictly speaking, the AP ASCOM driver should report 'False' when SharpCap queries the 'CanMoveAxis' property on your hardware, since the control box is not capable of running the commands needed to perform the move operations. Because it is returning 'True' for that property, SharpCap thinks that the move axis command will work and populates the list of rates and enables the movement buttons.
Fortunately it seems that the only thing affected is the move axis command (at least that's all we have noticed so far). That will really only affect two things in SharpCap - the movement buttons and the 'feature tracking' tool. Things like plate solving should still work, and you should still be able to use SharpCap to GOTO a target or set of co-ordinates as that uses a different part of the ASCOM driver that will hopefully work OK.
One thing you might want to investigate is the 'Pixel Position/Click to Recenter' tool - this uses plate solving to show the co-ordinates currently being viewed and allows you to recenter the view by double clicking anywhere in the current image. This again uses the GOTO commands of the ASCOM driver, so should work.
cheers,
Robin