Potential conflicts with existing filter configuration values in config

Problem/Motivation

I went to go look at my exported config and noticed that the list of content types are just at the root level configuration of the plugin:

      sorts:
        type__sort_bundles_weight:
          id: type__sort_bundles_weight
          table: node_field_data
          field: type__sort_bundles_weight
          relationship: none
          group_type: group
          admin_label: ''
          entity_type: node
          plugin_id: extended_sort_by_bundles_weight
          order: ASC
          expose:
            label: ''
            field_identifier: ''
          exposed: false
          content_type_1: '0'
          content_type_2: '0'
          ...

What were to happen if I had a content type named "relationship" in this case? I think the list of weights should be nested underneath a "weights" key to prevent possible conflicts with the existing out-of-the-box configuration keys provided by the plugin.