At startup VisualVM picks a JDK that it then decides it won't/can't run with

At startup VisualVM picks a JDK that it then decides it won't/can't run with.

Steps to reproduce the behavior:

1. VisualVM 2.0.6 and macOS BigSur (Had the same problem before with other versions)
2. Have Java 1.6, 1.8, 11, 15 and 16 installed.
3. When starting VisualVM will choose Java 16 to run with (since it the latest...)
4. Since Java 16 is unsupported it will then refuse to run...

a) There are 5 JDK:s available – 3 of which should work perfectly (fully supported). Why not pick one of those 3?

b) Why refuse to run with Java 16? Are you sure it won't work?

c) I have found and modified the visualvm_jdkhome property in /Applications/VisualVM.app/Contents/Resources/visualvm/etc/visualvm.conf
I shouldn't have to do this, but if I need/want to change some settings it would be preferable from
~/Library/Application Support/VisualVM/2.0.6/config

Start with /Applications/VisualVM.app/Contents/Resources/visualvm/etc/visualvm.conf and the visualvm_jdkhome property, then trace how VisualVM selects and validates an installed JDK on macOS. Check how settings under ~/Library/Application Support/VisualVM/2.0.6/config are handled. Done means startup no longer selects an unsupported JDK when a supported one is available, without requiring edits inside the application bundle.