I think I solved it. I reset the eqmod settings and then I found this in the eqmod docs:
Max slew rate (introduced with V1.21e)
Provided the “Show Advanced Settings” option has been checked on the EQASCOM setup screen the user now
has the option to limit the slew rate of Gotos and Parks/Unparks.
The way this works is that rather than telling the mount to goto a specific position, EQASCOM now just sets it
moving in the appropriate direction. It then monitors the mounts position until it has passed the desired target
position and then issues a normal goto. Because the mount is close to the intended target the slew is
implemented at a slow rate by the mount.
Please note that there are potential control issues in operating in this way. Whilst the standard goto method will
always stop when reaching the target position, this alternate method will only stop upon instruction by
EQASCOM. So if communications are lost it is possible that the mount will slew continuously. It is therefore not
advised to use this feature when operating the mount remotely.
This function was introduced at the request of those in extremely cold climates where the standard high speed
slews were becoming inaccurate
At any rate, (Pun intended), I think this was the behavior I was seeing. The problem for me is every goto was way off. Ill have to test it now and see if it not going past and then reslewing improves pointing accuracy. The weird thing is, this has happened to me on different mounts and different computers (and even different builds of eqmod). All ended up with plate solves taking quite a long time because the mount was several degrees off of the target.
Ill post back after I test under the stars.