As a workaround you can run blazor additionally on a separate port. Create an additional client blazor profile for this port and start the blazor app via
dotnet watch --launch-profile "otherPortProfile"
Details: https://stackoverflow.com/a/79429186/2534462