It's no longer useful and it obscures process-wide configuration of the EDK. All users should be updated to explicitly call mojo::edk::Init as needed rather than relying on a lazily initialized singleton to do it for them.