It's one of the unfortunate downsides of using the .NET Framework. The DisplayFusion Settings window has a ton of options and controls that need to be built before the settings form can be shown. Some of the time is waiting for the DisplayFusionSettings.exe process to be initialized, and then the rest is building all of the controls for the Settings window.

We could make it faster by having different windows for each feature, but we think that would be messy and not intuitive to use, so we settled on one window that takes a few seconds to load