Yes, as a general "textbook" statement, I agree with that. However, let's close that textbook for a moment and apply industry insight and context.
I am not disagreeing with the general statement you made, but based on my experience with such PDM systems, I would caution that an implementation that does not take industry-specific factors into account can do more harm than good!
Looking at what @leonardosantambrogio is designing, it looks to me like a frame built from an aluminum strut. Bosch, ITEM, 8020, just to name the most well-known manufacturers.
The aluminum frames often provide the structural backbone of machines, and then polycarbonate sheets are used to provide machine safety.
For reference, I've spent almost 40 years in manufacturing and 34 years of those as a mechatronics engineer, developing complex manufacturing automation systems.
Today I don't detail design machines anymore, but develop machinery and systems concepts. I develop cost models and write proposals. My go-to tool is Fusion.
However, the other 99.9% of the industry works with SolidWorks. In my company (~250 employees), I am the only Fusion user.
In SolidWorks, or Autodesk Inventor, you'd use the frame generator to create the frame. I've used SolidWorks since 1998 and don't know a single person who would design such a frame with individually modeled aluminum struts as external components.
The video I posted, which you should watch if you haven't, mimics the concepts of these frame generators but involves much more manual work. The "beauty" of it is that changing overall dimensions of such a frame structure - something that happens frequently in machine design - is very quick and fluent.
To get back to your "independently defined components" statement, what I often do is that this frame would be its own external document that then would get linked into an overall assembly file.
That file would then only contain other external assemblies and individual components.
For that sort of machinery design, breaking every single component into it's own external file would substantially slow down development.
It would also be extremely limiting if you would want to design a modular concept working with configurations.
Again, it really depends on how you implement working with external components.
For my work I use the full extend of Fusion's abilities and most if not all of my designs contain internal and external components and assemblies.
If you're interested I can explain the limitations of working purely with external components and configured designs in more detail.