How much of your compile time is due to FSYN? There are messages the fitter puts out(in the .fit.rpt) that say exactly how long it takes and an estimate of how much it helped. Note that depending on your settings, the algorithms run twice, so you might see two batches of settings. I'm guessing this is a large culprit, and you can quickly see how much compile time you would save without this(i.e. if your design was like those that don't need this option turned on).
You might be able to turn the FSYN effort down, or possibly turn some of the options off. Even if you then miss timing by a little bit, it should work in the lab.
The biggest impact is probably to put this core into a partition, possibly a logiclock region, and compile with FSYN turned on, possibly at the highest level. Then set it to post-fit(strict) so it is locked down(I assume you're not making changes to it). From there on out, run compiles with physical synthesis turned off.