We will not have the data of the page in the clipboard because there would a interaction with the server to get the next page and then the data for the previous pages is not present on the clipboard.So i think it would be an expected behavior.
Further to add on above explanation and suggestion, Let's take a hypothesis situation for understanding pagination and sorting behaviour.
Whenever data is loaded in the grid first time, properties containing pagination are set with order and paginated/sorted data is presented in the UI. User is allowed to traverse the next pages. But as soon as the refresh is triggered, the section need to reset all the pagination properties and configurations and the section is loaded with the refreshed data to display on the UI. And it is an expected behaviour in generic terms, as you can either get refreshed data for whole grid or last paginated value. Sort also need to apply on paginated value sometimes, this also restrict.
Could you let me know, what is the source of the data in your grid? If it's data page, then the pagination will be reset based on the load management strategy anyhow. We can't avoid this.
As suggested by some developers above, you can have refresh only the row/tuple of the grid instead whole section.