Personally I don't care if we activate any of them.
Only BIP that may be worth activating is BIP 65 for CLTV, but I still don't understand how that's better than nLockTime. If it's required for certain DEX then I will support it.
Currently I see no reason to activate segwit though.
v0.16.3.0-rc0 referenced above has set signaling of BIP9 to begin Jan 1 2019 and thus is within the time frame for signaling. BIP65 and BIP66 is coded to activate along with CSV via BIP9 bit 0, segwit on bit 1. If you operate a pool it would be most welcome to learn if there are any issues with the rc0 release. Although it warns not to use for mining it is perfectly safe to try and we have some confirmation of a few blocks trickling in (I'm guessing from solo miners and not any pools). This is the version that will be released if no one finds any issues in the near future.
Activating segwit allows a new generation of interesting transaction types. It's an optional type of transaction and since upstream already has it active and supported it would appear illogical to purposefully cripple it in the core software.
edit: I suppose a more direct response: Do you have any technical reasons for not wishing to activate segwit?