About accessibility of conformity, design systems and CSS “Base” units CSS tricks

My brain cannot help, but try to make connections between apparently inseparable ideas. And that’s what happened yesterday when I read:

What we have is:

• A semantic problem to say that individual components can meet WCAG. We may be able to ‘optimize’ a part for accessibility, but accessible experiences are composed of complete web pages that contain components that are designed to work together.
• The desire to automate all things in a design system. Update it here and it is updated everywhere. But there is still this issue to know whether changing a component into a design system influences other components.
• A reinforcement about a possible new CSS -“Basic” unit. The idea is to set one element as a “base” with which other elements can inherit his font -related properties as roots for a better vertical rhythm between elements, regardless of their proximity.

Makes me think:

• Could a basic unit in CSS components make components more interoperable? Like, if buttons can inherit his font size, depending on which other component it is? Sorta such as containerquery units, but without having extra wrappers in the Markup.
• Would that allow the changes to design systems to Cascade more flexible between components?
• Will properties inherited via a basic element, make components more optimized for WCAG conformity when they are implemented on a page with other components?
• Overlaps this with CSS @scope at all?

Sorry for the shower thoughts, but it is interesting to consider how these ideas work together.