On reflection I feel content is best considered the data separate from the tools and presentation in your formulae;
However since tiddlywiki’s unique structuring allows information to be extracted from the data - and once visible, “information” is perhaps also content this get a little more complex.
However I think anyone designing a wiki can be carful not to unnecessarily mix data / code / presentation + tools so the data is always available to be exported and used elsewhere.
Because arguably new information can be created in tiddlywiki, then providing the user with a method to export both data and new information for use elsewhere is helpful. That is have your content and export it too.
Keep in mind tiddlywiki rests on standard internet protocols and standards to run html/javascript/json/css so even if superseded I expect the technologies and tiddlywiki will remain for a very long time, and given the tiddler is the basic unit, stored in plain text JSON records in a text/html file, the content will remain accessible as long as the JSON standard remains, and beyond, because it is easy to reverse engineer JSON anyway.