Scrivener already remembers the cursor position automatically, but there are one or two limitations which you may be consistently running into, depending on how you work. Note the explanation for why that is, at the end of this thread. I didn’t go into it in depth there, but there are technical complexities with storing the cursor position in Scrivenings view as well, once you start to consider all of the different scopes within which the canonical cursor position might be placed, up the chain of folders to the top level, never mind collections, that would make offsetting the value in real time difficult to do efficiently.
Since there is already a spiderweb of different threads on this, I’ll close this one and encourage any further conversation in previous threads.