I agreed with @Alessandro 
if you would like to access that wsl path from the command line, you would need to map that network location into a “local drive” .
You could use the command with something like this:
net use z: \\wsl.localhost\docker-desktop-data
(you may change the z: part with any local drive you want to map/assign for that network path - as long as they don’t exist on your local computer).
After that you could just go to that new location you just mapped to that wsl network path, e.g.: z: (or your chosen one)
and in that new drive location, you can just perform cd command to data\docker\volumes\DevKinsta\public and you will see your site folder mysite
Like this for example:
Also, you would be able to see that drive you mapped to wsl network path, via windows explorer. Like this for example:
After that, I’m sure you should be able to edit the site’s files (php scripts, etc.) with your local editor/program - as those are now accessible under that local drive that’s mapped to WSL network path. So yeah, it’s actually not DevKinsta related issue but that WSL and network mapping related.
Hope that helps 
Regards,
Agus