That video is absolute garbage..
Your reaction is quite typical unfortunately. He makes quite a few good points. He also missed quite a few of them but, he is much more often right than wrong.
He has some sidepoints that IMHO should lead him to the conclusion that anything driven to extremes just invites trouble. (like if you should invite an overarching OO structure into your OS)
As a result, he just goes to a different extreme, and falls of the rails.
And yes, the video is crap, excrement etc. At least the first few minutes that I could bear. Too much unrelated cases, too much paranoia, too other unrelated stuff dragged in by the hairs.
If you want to make a point about OOP vs procedural, make a point based on building an application in either. Leave out the bosses, winapi, and US-as-a-nazi states pictures etc. (that was when I stopped watching, but I was already skipping ahead). Simply because it is irrelevant and not the level where most people work (and I doubt he has experience on that level either). Stick to what you (and your viewers) hopefully intimately know.
I also think the state minimization argument is weak. That is not a unique aspect of procedural programming, other than that it nowadays attracts minimalists that bother. (Well at least they upgraded from asm. Took only 40 years)
If tomorrow OOP becomes the minimalists next sweet spot, I'm sure they'll use the same arguments :-)
One of the first shots was the most interesting, but afaik he didn't delve deeper into it. I do often feel that information hiding/encapsulation (and then specially investing heavily in _language level_ encapsulation
by default) is the least necessary part of OOP practices.
Specially in one (major) programmer projects, people always drone on on how in the future multiple other people might use the codebase and benefit from it, but my experience is that an aspect of the codebase is not stressed on a daily basis, the quality of it (iow classifying encapsulation visibility of fields/methods) will be very low.
OO should be about modelling and design, the language features are only helpers. People tend to overfocus on them.