Thanks!
This looks, at first glance, to be similar to an issue that will be fixed in SonarQube 10.5.
sonar.java.jdkHome is documented here.