The problems are that VS setups don't let you build your own customized dialogs to show at the start, and don't let you run code to populate them or validate the contents. That means you're not really using the setup project because you'll end up writing your own code to do all this. Although you might be tempted to run this code as custom action, it will run with the system account (in an Everyone install) and the dialogs won't work properly because you'll not be running in a Windowing STA context. So you could integrate all this into the setup if you used another tool (such as WiX) and designed your own dialog to show during the standard install dialogs. The general design pattern is that you collect the info and stoer it into properties that are used with cusom actions in the execute sequence to make the changes. This happens to enabled silent install, specifying the property values on the msiexec command line or group policy delivery.
With VS you'd be better off having the user run your code to configure all this after the install at first run of the app.