You could use another process to do this for you.
"Another alternative is to log the data to a *.blg (binary) format on
the local disk of the machine that you’re monitoring, then
post-process it later."
http://blogs.msdn.com/b/granth/archive/2008/09/23/relogging-perfmon-binary-log-files-to-sql.aspx
Now, the relog process will presumably hammer the crap out of your DB when it runs if you configure as above : once a day. Maybe you configure perfmon to restart once every 10 minutes, and then have your copy-and-relog processes configured similarly.
At any rate, you should test out different scenarios on a test SQL server, if you're concerned about impact to production and want to get this right the first time. Either way, you can only spread out or concentrating the load, not reduce it. All those writes will hit the SQL server, from my reading of it, it doesn't seem like it will do a BULK INSERT, from the documented command line options.