The key is this: (from the docs)
https://docs.oracle.com/database/122/BRADV/user-managed-recovery-advanced.htm#BRADV225 "You can recover backups through an OPEN RESETLOGS operation so long as:
- You have a current, backup, or created control file that detects prior incarnations
- You have all available archived redo logs"
So the control file has details of:
- incarnation "1", and its archives
- incarnation "2", and its archives
and so forth.
So if you restore a database back to incarnation "1", then the control file can 'tell' the recovery to roll through the archives for incarnation 1, and then proceed onto incarnation 2 and continue with those archive logs.
You are correct that if you don't have this information in the controlfile (or do not have a means of resurrecting it), then once you start attempting recoveries with incorrect incarnations you'll run into problems.
Gavin Soorma has a nice blog post on it here
https://gavinsoorma.com/2011/10/recovery-through-resetlogs-and-reset-of-the-incarnation-of-the-database/