I have been a programmer for almost 20 years working with Windows development, it's not that difficult as the windows drip is extremely slow and the overall architecture does not change that drastically. I have requested a refund. Needs to be stated on the purchase page, period.
If you use insider builds it would be expected you are aware you may encounter issues with software compatibility and pretty much any software company support will tell you to revert to a release build in such a situation. It should always be assumed that if a software page says Windows 11 that it means officially released and supported versions. This is true of Stardock, it will be true of Adobe etc.
Not even Microsoft support the beta/dev channel builds of Windows so it is hardly reasonable to expect others to do.
This is such a situation where the OS you are using is significantly different in that one area which is why the features are disabled.
In this case the taskbar is actively changing from build to build in the beta/dev channels which is why the software detects it is the 'new' taskbar and knows to disable those options for now. Whilst the OS itself may change slowly, some parts change more rapidly when under active development and the new taskbar simply isn't finished yet. Supporting it fully is simply not economically sensible as you can end up dumping work when they cancel the new features (as they did with that new taskbar last year) and chasing a constantly moving target.
