Content Deployment will always copy the most highest major version and the
most recent minor version. Depending on the timing of the jobs some major
and minor versions may be skipped. Depending on Security users will view
either the major version or the minor (draft) version on the production
site. But not all versions will be on the production site. This isn't a
problem because you wouldn't want to try to revert to a previous version on
the production site anyway. Any changes, including rollbacks, need to be
driven from the authoring/staging environment.
As the remarks on this site point out, the change token is used to limit a
query of the change log to either get all the newer changes or all the older
changes. It establishes a point in time. I assume you are looking for a
previous token so you can figure out a point in time to roll a list entry
back to. The change token really doesn't support that. You can revert a
list item to a previous version, but that is considered a new change, not a
rollback.