exclude module from timing synthesis

I believe your idea is wrong in the first place. All logic must pass timing on its clock. There is no concept of one section being more important than another. A module may be deconstrained if say multicycle can be applied. If you are failing timing on some paths fixed from build to build then you better tackle that directly. If the paths migrate from build to build then you may have reached the limit of your design/device.