It is an interesting proposition, worth trying. To be fair you are compering a badly written user story to a nicely written Job Story:
When I find an item I want to set an estimate for, I want to be able to see it, so that I can confirm that the item I’m estimating is actually the correct one.
As a moderator, I want to select an item to be estimated or re-estimated, the team sees the item and can estimate it.
The benefit is mostly because in the Job Story you are being more verbose; you could do the same in the user story:
As a person looking for an item I want to set an estimate for, I want to be able to see it, so that I can confirm that the item I’m estimating is actually the correct one.
The main point to me is that the format becomes less relevant when there was a conversation behind the story, ideally the story is written together. Also a user story is not only as a…I want to…so that…, it is enriched with acceptance criteria, BDD scenarios and all the relevant documents that provide context. Thanks for sharing your findings