TimeQuest range values for time values

With this restriction, your setup requirement is limited to 2,147,483.647. There is no path that could ever not meet timing, so if you reduce the -divide_by to get something in this range, it really doesn't matter. Your positive slack will still be in the millions.

(You might need to worry about hold times, since it looks like you're gating a clock...)

The limitation might be there for a reason(it might be a range that allows the TimeQuest enginge to run faster, or something like that.) You can file an SR to have it increased, but again, you could modify your requirement to fit that range without problems.