My belief is that you are inserting the gating logic by UPF, please confirm. If so, then I believe you have mixed in upf language.
Otherwise if you doing by verilog, then may be the tool doesn't understand whats is going there so you need to give sdc constraints to tool, to allow the tool understand where is the false where is the real path.
Sorry to say this but your question is like from a 5 year old kid. If someone asks you "my car has a problem. Please let me know how to fix it", can you give him a solution ?
why r u bothering about hold violations at synthesis stage ?
Clock gating hold violations can fixed like other hold violations during physical design phase.
Techniques can used to fix hold violations are clock skewing/buffering in data path near to endpoint.
yes..no need to bother about hold violations because clock is ideal during synthesis (no CTS). All hold violations will get fixed in post route database.
I think the first step is finding out what caused the hold viols. If it's a simple hold viol, ignore it till the backend, but if it's caused by other reasons, most likely required to fix them.
The problem is the OP didn't even provide the details and there is no way to help.