Good grief, I thought, I never knew that. Then I got to thinking that I surely would have noticed and anyway it would mean that the form and the recordset were out of step, were not synchronised. So I did some rudimentary tests and happily watched the record selector go up and down a list of records on a continuous form using Me.Recordset.MoveNext and Me.RecordSet.MovePrevious.Using rs.MovePrevious instead of the DoCmd won't move the recordselector on form.
Then I realised that you were referring to the clone, so let me be pedantic (am I still allowed to use that word?).
Any movement, however caused, of the base pointer/cursor of a recordset will be reflected on a bound form. Any movement of a cloned pointer/cursor will not be reflected on a bound form - it's the whole point and power of clones.