Hi Joe,
1. There are ample CSS classes on the elements to allow them to be styled. If you are not a CSS expert you may need to hire one to pretty up the forms as you would like. You might check with Joe Davis of i7MEDIA for a quote as he has a lot of experinece with styling Form Wizard.
2. The way the export works is we first create a DataTable and then we have a routine that can convert the data table to csv. The problem is there are rules about what column names can be in a data table so we cannot typically use the questions, so intstead we add the questions as the first row of data. Since the question text can be rather long, we also have a setting in the settings where you can enable question aliases, then when enabled you can edit the form and put shorter words for the aliases and they will be used for the first row labels instead of the long question text.
3. I've added a request for tab delimted export to our project tracker.
4. The Delete button should be a button not a link, it does postback a link does a get request, data should not be changed by a get request. A link is appropriate for a cancel if it is just a link back to the page or previous page, generally no postback is needed for cancel. Deleting data requires postback and a button is more appropriate. Though there is such a thing as <asp:LinkButton, I never use that anywhere because it doesn't work if javascript is disabled whereas button always works. A button can be styled from CSS to look like a link if really needed anyway.
5. That can be done with CSS like this:
.formresults a { display:block; }
6. You could set an end date on the instance of Form Wizard Pro and it will be removed from the page when it expires and you could have another instance published on the page with a future begin date so it starts the same as the end date of the first instance. This can be done from Administration > Content Manager, find the instance and click the publish link.
Hope that helps,
Joe