CSVs being created with a semicolon instead of a comma was supposedly
confirmed as a bug but doesn't seem to have ever been fixed because it happens on my install too. The quotes are normal to ensure that any instances of the seperator that are part of the actual field value are treated as such.
You can tell PowerShell to import the file using a semicolon delimiter as follows:
Import-Csv -Path $ExportFile -Delimiter ';'
It will then import normally just as if it was correctly formatted with commas.