Agree with many of the points here, persisting the collapsed state would make it a lot easier to find where you left off and orient yourself after navigating to different pages.
I kindly disagree that the two feature requests are the same. It might be nuanced but if folks want to help the logseq team it is important to think about these nuances and outline tradeoffs between competing approaches. Otherwise the logseq team will have to think through the details which undoubtedly creates more work.
In my opinion always collapsing subtrees is the wrong default. It creates the same kind of problems as not persisting collapsed state: you come back to a page that looks different than how you left it. To me that’s a clear loss in terms of usability and enabling people to use logseq efficiently.
EDIT Interestingly it seems that logseq does maintain the collapsed state under some circumstances.