Figure 34 shows that the PubSubCommunicationAttributesConfiguration is referenced by the connection, !not! by the endpoint. Several connections could share the same attribute.

Yes to "I think it is more likely that the AutomationComponent has one communication address in a ConnectionConfigurationSet and that the parameters like QoS and PublishingInterval are the same for all connections in one ConnectionConfigurationSet (or a small number of variations)".
In this case the CCS would have one PubSubCommunicationAttributesConfiguration, and all logical connections in the set reference this one.

In call agree that no actual change needed, just maybe add some text to better explain why it is constructed as it is

Text in 6.8.2 reads:
The ToCommunicationAttributesConfiguration reference is used to link a ConnectionConfiguration to a CommunicationAttributesConfiguration (see 6.14). This reference defines the communication attributes to be applied for this logical connection. Multiple ConnectionConfigurations may reference the same CommunicationAttributesConfiguration (see 5.5.6.2 for more details).
NOTE For an overview of how to configure the various connection types, see Annex D.

The second example in Annex D.1 shows a shared PubSubCommunicationAttributes (will be provided, whenever we include the Annex to the main spec)

Added to 6.8.2
Such they share the same set of attributes (e.g., address, QoS, interval, or timeout) and allow for example that connections are aggregated into one NetworkMessage (see 5.5.6.2 for more details).

reviewed changes in call, agreed to text and closed