The effect: attempting to start a pod from the DC/OS UI with a healthcheck interval below 20 (the default timeout) leads to an error message:
This is not an obvious error, since the user is now on a different screen from the health check. It's also an unnecessary constraint. There's no need to constrain the interval to be less than the timeout, since they run in sequence.
This is the pod definition which we were attempting to deploy.