In the end, instead of solving the problem I decided to avoid it. The second page in my app provides details on a table in the first page. As I described in this post, I have a link in each cell of the main table that contains the column and row as part of the URL’s query, and these are used to build the details object shown in the second page. I was using a dcc.Link to get to the details page, and the problem was that returning to the main page meant that its state was lost.
All I did, then, was replace the dcc.Links with html.As with target=_blank. This way, the details page opens in a new tab and the main page remains in the previous tab retaining its state. Not too elegant, but it gets the job done for my use-case.