Description of the need
Now that config values can be overridden via settings.php, we've created a system that can also be very confusing for admins and editors. When a value is overridden it appears as though the forms are broken.
For example, when CSS aggregation is set to FALSE in settings.php, visiting the form at admin/config/development/performance appears as usual, but when I attempt to check the box for "Aggregate and compress CSS files" and submit the form, it submits as usual, and the message The configuration options have been saved. is printed to the screen. However, when I scroll down to the checkbox for "Aggregate and compress CSS files" it remains unchecked.
Proposed solution
@herbdool posted a proof of concept PR that contained some interface components that indicated when a config value was overridden. I'm not sure how far this proof of concept is from a workable solution, but I really liked where it was heading:

Additional information
This is a follow up to https://github.com/backdrop/backdrop-issues/issues/2805
Recent comments
Hi, so working through Amilenkov's useful suggestions in turn unpublished? - I can see the page itself when not logged in. I did then edit and added a menu link from the page...
menu partially working
Amilenkov's suggestions are spot on. As for the greyed out Menu module, that's because there must be another module that depends on Menu. Core will gray out modules that cannot be disabled (e.g...
menu partially working
Welcome to the Backdrop community! My first suspicion would be access to the destination page. Backdrop checks access when building the menu, so a link can be enabled but still be hidden...
menu partially working