For "BlitzMax" I think that's not a real 60hz, "BMax" just slow the game to 60hz without forcing anything ( like the WaitTimer() ). I use the
For Max, it first tries to force the refresh rate to what has been selected (ie 85)... if that's unsuccessful, it defaults to the first refresh rate returned by the OS/drivers... which is usually 60. In that case, Max will run the gamecode internally at 85 still, but the refresh rate is only 60. It is hoped that in the future Max will try to pick the closest refresh rate that matches the one desired by coder... ie if coder chooses 105, Max would pick 100 if the drivers/OS/monitor supported it. The only danger here is when the drivers lie and say the monitor can support a mode when it actually can't.
And while you're correct about all computers supporting 60hz (afaik) there could be a combination of resolution/bitdepth that can't be supported at 60hz, which could cause problems regardless. Of course, then it is up to the drivers to report correctly that that resolution can't be supported. If they don't, and a monitor fries, it really isn't Max's fault.