The reactive refresh behavior you're seeing is by design in Celigo's HTTP Universal Connector. There's currently no built-in UI setting to configure proactive/preemptive token refresh or an expiry offset for Client Credentials flows.
Also, check out the community post — it might be helpful.