No. That's just a nested ordered list. The difference that occurs when we all agree that it's also a ToC is night and day. You can also create custom elements, but again, if nobody has consensus on the meaning of those elements then they're just elements.
That means that as a client I am not empowered to automatically display your content in a new way.
A ToC is more important than a list and should build a graph to other parts of your document. If the only agreement we have is that something is a list, then we've reduced the semantic meaning of a list to the question of whether we should have visual signifiers like bullet points or numbers.
I want the niceness of Wikipedia generalized elsewhere but abstracted by my client or browser. The more we agree on the precise meaning of elements, the more we are empowered to programatically redesign or interact with content.
Screen readers actually do generate a couple of different things that you could consider a ToC from the semantic meaning of various tags. If you structure your document properly, it's not a terribly difficult task for the browser to generate it. Apple showed that Safari 18's reader mode is going to have one, actually.
That means that as a client I am not empowered to automatically display your content in a new way.