When you say they are only used for setup...do you mean setup on the user side or on development side when coding?
The same dialog is used for both design time and run-time purposes.
It seems like we are now stuck with having to display forms that don't match the rest of the application if we choose to use your security add-on.
The framework does fully support the DevExpress controls. You are not "stuck" with using any controls you do not wish to. As far as security is concerned, this is an add-on module and is more of an application rather than just components, such as a text box. We went to great lengths just to provide the BrowseDialog in DevExpress format. This is more of an application component, but we went ahead and added this functionality since it is part of the framework.
We will be releasing Application Themese relatively soon which the Security repects since it uses the StrataFrame controls. You could create your own theme class (just a class with a lot of properties being set) to make the security follow the DevExpress colors.
On a final point, the development team spent several months on this module, which is a steal at $295. I would not throw the "baby out with the bath water" just over this one thing.
When we were going to use DevExpress controls, we were willing to leave the setup dialog in the StrataFrame controls as this is not something you spend any time in, other than initial setup.