2 hold checks - why?

The documentation, and TimeQuest in general, is designed to handle all sorts of complicated issues that are rarely done in practice. I find most designs the clock requirements are quite simple. And in the complicated cases, users spend a lot of time looking at their constraints, drawing it out, and trying to figure out what's going to happen. It's so much easier to just put in a first guess, run it through TimeQuest, and see how it uses it. If it's not what you want, make a change. Multicycles are a great example of this, where it's often easier to just put in a value and check it, then understand all the possibilities of what a Multicycle can do. (Just be sure to check setup and hold...)