I guess i didn't understand your workflow correctly. But in general, configurations allow you to modify the DAML when ArcGIS Pro starts up, but before the UI is activated. This allows total control over the DAML content and hence the UI. Add-ins are still loaded even if you run ArcGIS Pro with a Configuration, but you could modify the DAML of those Add-ins too (since the Add-in DAML will be included when Pro starts).
Now states & conditions can be used to control the visibility of Tabs, Groups in an Add-in (no need for a Configuration to do this). This ProGuide is talking about tabs and groups: ProGuide Ribbon Tabs and Groups · ArcGIS/arcgis-pro-sdk Wiki (github.com)
If you use a condition on an ArcGIS Pro button you can only disable the button, but you cannot hide it (or delete it) by using a condition. But if you add your edit button (like the 'Delete' button) to an Edit group you can hide the whole group. To test this out i modified the 'working with daml' sample code and hooked a new group 'myEdit_group' to the existing state/condition of the sample. I can now use the 'Toggle State' button (which changes the condition) to hide or show the 'myEdit_group':
after the toggle:
This is the DAML that does the work:
<group id="myEdit_group" caption="My Edit Tools" keytip="X1"
condition="example_state_condition">
<button refID="esri_core_saveProjectButton" />
<button refID="esri_core_saveProjectAsButton" />
</group>
and this adds the group to the mapping tab:
<updateModule refID="esri_mapping">
<tabs>
<updateTab refID="esri_mapping_homeTab">
<insertGroup refID="myEdit_group"/>
</updateTab>
</tabs>
...