Whether or not you can do it in a view somewhat depends upon which database you’re using. For example, in PostgreSQL, the autoincrement value is stored in a database “sequence” object.
You would need to write raw SQL to do this to alter the sequence value for that field.
However, I’ll point out from a database perspective, it should never be necessary to do this. If you’re concerned about the primary key starting out at 1, you’re wasting mental energy worrying about something that shouldn’t be a concern. A numeric primary key of a table should have no semantic meaning - not even to identify sequencing.