I have a feeling that this goal is useful for only a quite small minority of TiddlyWikis. There are some that are definitely hierarchical. I created one along these lines (https://charter2024.andoverct.info/), and am working on another (https://crosseye.github.io/rham-policy/). But I think such wikis are rare.
On the first tiddler of the first TW most users see, TiddlyWiki is described specifically as “non-linear”. And I think that covers most usage of it. While they might have some hierarchical, linear sections, wikis tend toward random access and surfing.
Think about tiddlywiki.com. How would you arrange a linear overview? The TOC is arranged for skimming and searching, and it’s definitely not hierarchical. And if you did still decide to print it in a hierarchical manner, would you print three copies of Filter Operators because it appears under Filters, under Reference > Filters, and under Reference > Concepts > Filter? If not, how do you decide where it goes? And of course with transcluded content, would you expect to repeat it everywhere its used or somehow change it to a reference?
It’s not that I think this is a bad idea to have, but I think its scope is fairly limited. And I’m not sure how to make it generic. My two wikis that are so hierarchical are still fairly different. The charter has a fixed hierarchy. Chapters consist of sections; sections may have subsections, and subsections may have sub-subsections. Each level has a consistent numbering scheme. The policy manual has sections, which contain numbered policies. Policies are usually broken into sections, some numbered, some not. Those sections may be subdivided, and those subdivisions themselves may be, and so on, without a fixed hierarchy. Their numbering is inconsistent. Some use roman numerals, some use arabic numbers, others use letters.
I have a difficult time imagining one macro/procedure that would easily handle both of these, never mind all the other possibilities users might have for hierarchies. But I do have a print stylesheet in place for the charter, and at least the start of one for the policy manual. Because these are linear, hierarchical documents, and can be displayed that way, this is important.
I just feel that it would be hard to capture a general mechanism that wouldn’t be to constricting. But the TW community continually surprises me, so perhaps you’ll be able to come up with something.