Just a thought here.
We market ourselves as a Content Management System running on our Community Portal Framework. We do not think this is deceitful, when a client asks about what we are running, we tell them it is a DotNetNuke based environment. We obviously do this for marketing purposes. If we announce we run DNN, then potential clients would search for cheaper (and maybe not better) providers.
We offer well over 50 modules. We try to carry that through in the modules we offer. Currently it is not an issue with your modules. We manage 2 sites that we are using the registration on, and the other is very familiar with DNN. The remainder of our sites use the standard registration. However, as we start to market this service, we like to market in a manner that shows a complete package, and not a "duct tape" solution with a bunch of bells and whistles.
What are you thoughts of not showing this is a Data Springs module on the initial screens?
Just some thoughts.

Well actually you can control all of this as 'Localization'. We make the new wizard easy to find documentation, learn where the latest user guide, and maybe add a few links for demonstrations on the main page but this is just a literal that can be modified in the resource file (under desktop modules/ dynamic registration/ app_globalresources/Dynamic-Registration.ascx.resx). I would suggest opening that file in notepad and branding it to maybe your site and company. This would not be against the license agreement at all however you would need to purchase the enterprise license or be an enterprise license customer if you install the module on multiple instances of DNN. The only downside to this approach VS us just not including anything would be that you would have to retrofit these changes after each upgrade. This should be minimal though since there is no actual 'code changes'.

-Chad