Exactly. I'm a big believer that state-as-an-implementation-detail is a code smell, but that if your program is fundamentally concerned with state (as UIs nearly always are), you should equip yourself with tools that let you ergonomically manage that state instead of trying to sweep it under the rug and pretend it doesn't exist. Hooks feel like state-denialism to me.
> and that state management is going to get to hardwired to the UI component library
I don't really see how that's a different state of affairs than class-based components. You just do this if you wanted...
const [thisState, setState] = useState({});
...and its uses would generally be semantically identical to state-based stuff without hooks.
There are some good solutions to state management that are complimentary to React such as XState and it really should be dealt with as a separate concern from a UI component library.
I am concerned that React's object based approach is going to become a second class citizen in lieu of Hooks and that state management is going to get to hardwired to the UI component library.