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
No problem, let's see how it evolves. I'd be happy to provide a suggested version if i could. I will keep that in mind and try learn this hook chain hopefully very soon. I will...
File hashing uploads made through TinyMCE
I could request hashing support, but that's the lazy way 🤣 I would appreciate it if you as an active maintainer would 'officially' add a hashing support...
File hashing uploads made through TinyMCE
Hi, i understand the updating obstacle - not worth mentioning - hence it is a wacky (but working) patch until i know what to do. :-) One of my biggest wishes is to understand the hook...
File hashing uploads made through TinyMCE