So as a follow up, it appears there are no plans to support WSL2 on drivepool at this point in time: https://community.covecube.com/index.php?/topic/5303-wsl-2-support/&do=findComment&comment=31779
I decided take a plunge to find out if WSL2 worked with Windows Storage Spaces. I came across this error 0x00000057, while doing anything within the GUI, so unfortunatley had to quickly get up to speed with creating the Storage Pool and Storage Spaces through PowerShell.
Long story short, it did not work with Storage Spaces. Maybe WSL2 does not like virtual drives???
I have temporarily resorted to a pooled storage using Dynamic Disks, set up with a Spanned Volume through Windows' Disk Management utility. I suppose this is sort of a virtual drive, but it works with WSL2. Spanned Volumes are basically DrivePool without arms and legs. You can't balance or choose where the data is stored on the drives, therefore if one disk is near EOL, the whole volume will need to be re-created.
While typing this up, I just realised I should have done a reset of docker to factory defaults first... I might revisit storage spaces at a later date
