That's true with the ModuleSettingsInitialize()

However with the other UAVOs the standard has been to _only_ initialize them in the module that sources that data.  This avoids bugs where you are listening to a UAVO expecting it to have some data and it doesn't have any.  This results in annoying asserts failing (which locks up the flight controller) when debugging but avoids much more dangerous bugs in flight later.