Adding a UserCommand to convert etl files to speedscope.json or updating NetperfToSpeedScope

I've noticed that there is a UserCommand called NetperfToSpeedScope however giving that method a provided etl file, as it is stated in its comments results in an error due to the etlx file not being found. I am unsure if there is a way to give the UserCommand a .netperf file since as far as I can tell from documentation the .netperf format is deprecated but this would likely cause the program to also look for a .etlx file which may not exist since I cant find where these are generated.

My main question is, is it worth the time to put in a PR to add a UserCommand to convert an etl file to SpeedScope, or does the current method work but need some more specific files that I am not looking for?

If NetPerf is not deprecated, how would I obtain this data using PerfView so I can quickly convert traces to the SpeedScope format?

Start with the UserCommand named NetperfToSpeedScope and its comments, then trace how PerfView handles .etl, .netperf, and .etlx inputs. Determine whether the existing command supports the reported workflow or whether a new conversion command is needed; done means the supported input path and resulting speedscope.json behavior are clear and reproducible.