Question about Monitor

I'm not sure what a "timing relaxation tool" is? If the period is 10ns and the setup is 10ns, then that's what it needs to meet. If you're design runs where it sends data every other clock cycle or something like that, then two multicycles can be added to make it a 20ns setup and 0ns hold.

For paths between clocks, false paths are valid if your design treats it asynchronously. For example, you might have two 10ns clocks with data going between them through an asynchronous FIFO. That would allow you to cut timing between them. If you pass data directly and need it to get there in a cycle, then you can't cut timing. Obviously if the clocks are truly asynchronous, there is no way to pass data synchronously regardless of what your design expects, so the false path needs to be there and the design needs to handle the asynchronous nature. But multicycles and false paths are telling TimeQuest "what you designed for".