Crashes are not the only way to lose the tab history. Any time I have to close and reopen X2 the history is gone. Sometimes, the slow responses of the remote servers I access prevents X2 even from restoring the tabs to where they were when the program closed.
You've mentioned you have limited network configurations available for testing, so I somewhat understand your reluctance to put the effort into something you feel isn't beneficial. On the other hand I deal with multiple servers (10's) with many folders (100's) each week. The bookmark facility in x2 cannot handle the number of locations so I use bookmarks to get to the approximate location and walk the tree from there. The bookmark facility is a static list of locations, but I deal with dynamic and changing folder names so that also limits the usefulness of the bookmarks.
The slow response from the servers makes this process much more painful than if all the files were on a local drive, and it's a daily fact of life for my workflow.
Again, I fail to understand why, when you already save tab history within a session, extending this history across sessions is not an obvious enhancement. But then, from my point of view, it's just a "simple matter of programming"
-----------------------------
PJ in FL