What you are asking for simply does not exist in the cmdlet in your question.
Never assume a cmdlet can do X or Y. Use the help files to see what params/switches it does allow, anything not shown, is not natively possible.
You'd end up needing to write your own proxy function to extend for what you are after or submit a feature request to MS. Unless enough folks upvote such a feature request, it won't happen in most cases.
Why go through the Excel trip, when you can parse XML natively in PowerShell?