Only if Asobo doesn’t change anything.
Everything you suggested might be correct, but it doesn’t mean that such changes need to be breaking for existing addons.
You can introduce a new addon structure while still supporting the legacy one.
You can introduce new autopilot logic by versioning it instead of changing it globally affecting and breaking every aircraft that they didn’t actually update to adhere with the changes (which affects everything third-party).
If you don’t manage to make something backwards-compatible, give everyone a heads-up about changes and provide a migration/update HowTo.
All of that is no rocket science.
IT development in more complex business areas does that every single day since interfaces, functions, etc. always change and still they manage to not break everything around them with a single patch.
Of course it requires more effort and time to do it properly, but then again MS/Asobo highly benefit from the addons and mods since without them MSFS would not be accepted by most simmers.