Unless you've already learned React with class components and lifecycle methods, I suspect it simpler to just not learn them and learn functional components and hooks. It's extra stuff to wrap your head around if you learned the old way first, sure, but it's not fundamentally more complex on its own.
The official react docs and tutorial don't help here since it introduces class components first.
In class-based components “didMount”, “willReceiveProps”, “willUnmount” et al. would be more or less intuitive to a newcomer with just a general idea of how it works.
That I believe makes FCs fundamentally more complex to learn from scratch.
Personally having some experience I go with FCs if there’s a new complex front-end project that is based on React, but I use class-based components if I need to sprinkle a few on a mostly static website that may have to be maintained by someone else.
(Class-based components in a basic case, which would be the case in question, are also quite straightforward to convert to FCs.)
Anyway, the standard is there and apparently being worked on so I fail to see how it entirely isn’t a thing—hopefully another incarnation will land.
All around it just feels like a solid way to bundle all the aspects of an element together.
For a minimal start there’s no need to adopt JSX, wrap your head around hooks and functional components, or deal with Webpack configuration. Just add ReactDOM and React scripts, alias React.createElement() to something short like el() for use in render() methods, compose your components and render them at the desired root if user agent has JavaScript enabled[1].
You have the freedom to move the whole page to React later, implement server-side rendering and so on, but you don’t have to.
That said, yes, you will be pulling React, which will consume extra bandwidth, and to stay crawler-friendly your React components ideally should replace and improve functionality already provided by the static page in a more basic way.
[0] Perhaps you can see your application growing complex enough and you suspect React would be easy to hire for if you need additional help, etc.
[1] To preserve compatibility with older browsers but write components as modern classes, you could add a simple frontend build step that runs Babel on JS files with a single preset "@babel/env" specifying your target browsers.