there is a similar problem for singleton configurations as we've solved in for configuration collection items.
steps to reproduce the problem:
this configuration exists initially in the sample content of the sample app
delete this singleton configuration
open the configuration "Sample Configuration" again for the sub-page
it looks then like
what is misleading:
mixed display of inherited and non-inherited properties, although property inheritance is not enabled
when property is edited and saved (e.g. in DAM path), and the configuration is loaded again only the new value is displayed, the other values not (until property inheritance activated)
it would be nice to apply the same handling as for config collections:
if the whole singleton configuration is inherited in one piece, the whole configuration block should be disabled, and a text displayed like "This configuration is inherited. Click here to break inheritance".
When this break modus is entered enable property inheritance is activated by default (but can be deactivated before saving).
the behavior should be as consistent as possible to that of collection items