If you're using an atomic deployment practice, then you must de-activate Breeze before each deployment. If not, you will see errors such as "Cannot redeclare breezegetcachebasepath()" on the front end after the new release is activated.

Here's what the support team said back when I reported this issue:

"Basically, the option which allows setting cache path at their own config path is not available in Breeze. So right now only the option deactivate and activate the plugin after each deployment."

This feature should be implemented ASAP. It's a common feature with other major caching plugins such as WP-Rocket.