Consuming the WSL API requires developers to populate the distribution name parameter for most functions. There is no API to retrieve a list of valid distribution names, however, and none of the APIs support a nullptr input to signify the user's default distribution should be used, as general Win32 programming patterns would nudge you towards.
How are developers meant to consume these APIs? The dev story seems incomplete.
Trick to turn this tag feature, contrast death by tag discussion ref #3515, is providing the use case for your AP change request. [With no implication there is no use case. But that's how the dupe died two weeks after it was opened.]
This submission is spiritually similar to #3515. #3515 was a discussion thread (label/tag 'discussion') that ran course and was closed. The hope is some use cases for the implied API enhancement are provided, thumbs up on the OP appear, and this one (which to be clear is entirely sensible) has a better chance than #3515. Question / observational commentary ("How are developers meant to consume these APIs? The dev story seems incomplete"), on a statistical basis anyway, usually end up chirping crickets.
+1 to enumerate wls list via the API. I'm building a remoting terminal that also supports WSL but I can't list them to the user without having to parts executable output. Would love if I could query for it instead of parsing text.