Same here, don't worry.
It probably has something to do with the step width used to scan the full span when the autotune function searches for the highest peak.
This search has to be performed quickly so these steps are quite coarse and probably the result of a simple binary counter, converted to floating point.
Autotune is meant to "find something to display quickly" not to make any accurate measurement, it just put you approximately there and then it is up to you to decide how you will setup the analyzer's parameters to best suit your intended measurement.
Same thing for the span and RBW, these default settings are used whatever autotune finds probably because they are the most susceptible to display something meaningful.
So, it's pretty much normal and has nothing to do with calibration error.
Besides, if you just do a peak detection marker, you will see that it is spot-on the freq +/- 1 digit.