SPMM
Yes, I don't understand your issue as you describe it. Furthermore I don't understand how it would compel someone to create another account as a work-around.
You say this, and I can only presume that this is the issue you claim to have, "When I reset the puzzle, (having saved my highest scoring solution), I want to start again from the starting pose and original starting high score. "
I don't see an issue here except that I have no idea what you mean by "original starting high score". Resetting the puzzle resets the current model to the starting conformation. The conformation determines the score.
What behavior are you expecting here and what doe you mean by "original starting high score"?
You go on to say this,"If I reopen a saved branch point, my high score does not revert to the score I had at that point, my highest score is still in place."
Of course your highest score is still in place. Why would you expect your high score to change just because you loaded another solution? Your highest credited score is your highest credited score. It makes no sense for that to change to a lower credited score. The 'highest credited score' is like the high water mark. It's just a record of what your highest score has been. It really has nothing to do with what you are currently working on.
You then say, "So the problem (for me) of the highest score and pose being retained is present either when reopening a branch save or when resetting a puzzle."
This sentence is just plain hard to read.
I simply can not understand why you think this is a problem or why you think creating a new account would solve this problem (that isn't there). I can't understand why would would expect your highest credited score to go away when you reset or load a different solution.
You go on to say, "Even if I manually save a puzzle immediately I open it; the A key will revert to the best highest score and pose on that machine."
The A key (also Ctl-B) will restore to your "Very Best Solution You Folded". What behavior are you expecting when you press the A key? And why would creating another account make the A key behave differently?
Then you say some things about how you play and also this, "Even if I saved every single one of those attempts I would still have the problem."
And this, "Given the range of save and auto-save options available I find it odd that the scores and pose of a saved puzzle do not reset to match the high score achieved when it was saved."
I still don't see a problem. When you save a solution you are simply saving the current conformation of the model. There is only one "High Score". Other scores that correspond to other conformations are saved with the conformation. There is not a problem that I can see.
Next and finally you say this, "When I save a document I expect it to be saved exactly as it was at that point, not to have later changes incorporated into it."
I have to presume that you are implying that your saved solutions have later changes incorporated into them. Where do you get this idea? How could this property even been implemented? You saved solutions are a save of the current conformation. There is no possible way that future changes could be incorporated into the file.
I'll go ahead and play devil's advocate here for a moment. Let's say these bizarre behaviors are taking place. Let's pretend that future moves done on a solution are somehow saved with the solution in the present. Let's say that you can't load the "original starting high score" when you reset a puzzle. How would creating another account help with that? Won't the new account also have the same problems that you seem to experience? How does the other account help you get around the problems you seem to have in the first account? You can't share solo solutions from one account to the other.
The descriptions of your perceived difficulties really don't seem to lead to a conclusion that supports having multiple accounts that compete in the puzzles.
I don't see a logical connection from a confused concept of what "high score" means and the need to run multiple accounts that compete.