Reading a summary of the book in Wikipedia/Blinkist/ChatGPT is definitely not the same as the reading book.
Sure, you may grasp at the central idea or argument superficially, but to understand it fully, with its caveats and nuances, and overarching context?
You can regurgitate but not assimilate.
You're putting way too much faith into people's intelligence (or projecting your own onto them) if you think people are picking up the nuanced bits just by reading.
Which still to the thread starts point. All of that stuff could be captured in a diff medium and to my point if it's worth capturing in the first place can be summarized and the additional stuff you're mentioning written as bullet points.
Of course no one - no matter how intelligent! - will pick up every bit of nuance. That's why engaging with what other people think (also a process!) about [whatever] is an important part of skill development. I don't think anyone is incapable of engaging in this - even if their sophistication will always be limited by their intelligence / affinity / time / etc etc etc.
This is a useful paradigm under which to consider other skills. Computer code (product) is (approaching...) wide availability from LLMs, but the skills necessary to be a good developer come through a process that involves independently solving problems and asking questions that have (at least at first!) already been addressed by others.