They instead seem to be the kind that appear on the page initially, pointing to a new device and explaining a new feature, until the user dismisses them. I don't believe they involve hover at all.
I'm still not personally sure how workable this is on a small screen (because I personally don't have experience with it), and could use some discussion or examples of how this has been done (if it has been done) on mobile. It seems odd to me too to write an article about UX these days without mentioning mobile.
But it is worth commenting on the trend of "initially visible tooltips pointing out new or advanced features." Personally, I almost always dismiss them without reading them, they are usually getting in the way of whatever I came to that site/app to do. I wonder if there is public research on their effectiveness.
__To me__ those might be tooltips in terms of implementation (i.e., code) but I'm not so sure I would consider them TTs in the traditional sense. They're more like "feature flags".
They are tooltips in the plain language meaning of the word, they are tips about tools. But I agree the term "tooltip" initially made me think they were talking about the appear-on-hover kind.
"feature flag" also means something very different in software discussions, I wouldn't try to re-use it for these. Words are hard. https://en.wikipedia.org/wiki/Feature_toggle
I might call them "feature disclosure callouts" or "feature announcement callouts" or something like that, but that's a mouthful. "callout" is one graphic design term for that bubble with a pointer annotating the the thing pointed to. https://en.wikipedia.org/wiki/Callout
For me personally it would be nice if there was a reliable way to detect a quick jab (tool tip), vs a press, vs a long press, but I could see this does not working well for people with mobility issues etc.
Tap the balloon and it expands with more detailed explanation.
The help mode could be triggered by a tap on an always present (?) icon somewhere in the corner.