In 11.5, there are more ways to control the order of loading saved variables (you can load them before the addon itself is run) ¹. As far as I'm aware, this is mostly handled by AceAddon and the event-based initialization right now. However, there are some potential issues which could be alleviated by streamlining the load order (important caveat: Treading careful here is mandatory as overwriting the saved variables would erase all data).

• Some users have reported errors where the DB wasn't available in time, causing errors. This has been fairly rare but it does happen; it's a typical symptom of async/interleaved code paths and should in theory be fixed if the load order is guaranteed to be sequential by the client
• In the code, there are some timers seemingly used to retry initializing the Options when AceDB hasn't loaded - could then remove these
• It'll be much easier to test that things are loading as expected; including the DB initialization and DB migrations (if implemented)
• Some of the initialization code could potentially be simplified, removed, or dependencies dropped - less code means reduced costs overall
• There have been difficult-to-reproduce issues with default values not being loaded as expected - another problem that may be avoided