TimeQuest issue need you help

My personal advice regarding multicycle is this:

avoid it unless you are really desparate with fmax then make it absolutely sure that it is applicable.

Unfortunately timequest has made it look like spreading chocolate anywhere one thinks and has diverted its concept for the sake of the tool's default behaviour.

Let me explain this point:Multicycle is not just matter of applying it when it sounds so but the design sampling phase must match the launched data otherwise your logic will go stray while timing passes.

Timequest borrowed multicycle idea to apply it whenever the default definition of current launch/latch edges are too restrictive such as clocks with different phases and rate. Timequest should also have been telling you that you the designer must in parallel make sure that you are sampling(latching) in sync with multicycle approach.