Yeah, you can. Kind of - a Child Actor Component can hold another actor. And any actor can own many CACs. But CACs may not be the best due to performance reasons and they can become unruly at times.
Perhaps actor components are a better choice. But not just actor components, consider overriding more specialised comps instead, and encapsulate behaviour inside them:
Another example:
The pins on those cube actors can be made out of components that support inheritance. They can have their own variables, methods, dispatchers and the entire logic that drives them, and also looks up what other components attached to the same parent are up to.