Yes, you’re right that would be useful. I’ll create an internal feature request for being able to "One-Click " update the MU Plugin.
So the main function of the MU Plugin is to handle the cache functions when your site is being hosted on Kinsta. It also detects when you are are using any banned plugins. The banned plugin list is hardcoded within the MU Plugin so that’s why updates are necessary.
Different sites may have different versions of the MU Plugin either due to manual updates or because when a new site is created the latest version of our MU Plugin is installed.
You can actually delete the mu-plugin when developing locally since there’s no caching within DevKinsta/there’s no reason for us to block plugins due to performance issues on your local environment. You would just need to add the MU Plugin back once you go Live on Kinsta.
You should be sure to add it under ~/wp-content/mu-plugins, though and not ~/wp-content/plugins in order for it to work as an MU Plugin.
Very odd that it’s so inconsistent. As far as I know the Mu Plugin shouldn’t affect any of those requirements. Very odd. I’ll test this if I can or at least keep on the lookout for similar issues.
Thanks for sharing and please let us know if more issues occur!