WorldServer - does the new Cached TM mechanism prevent Live TM Mode?

I read the release notes of WorldServer 11.6 and realized that the TM Cache mechanism has been implemented with it. I'd like to understand this new feature better. 

We are using Live TM mode for our translation workflow. However, according to the explanation in the release note above, if we introduce the TM Cache mechanism, which is a default setting, it becomes Non Live TM mode. I'm very confused. Could you explain the relation between Live TM mode and TM Cache mechanism?

Starting with WorldServer 11.6, a caching mechanism has been implemented to drastically improve TM lookup times. This article explains the new functionality in detail.

Moreover, note that you can disable the Cached TM feature by configuring the Segment Asset step if required, as described in the documentation. The Cached TM functionality has no impact whatsoever on Live TM mode. You will still be able to update your TM upon each import of a return package or Save action. It is an additional feature to improve your user experience.

We strongly recommend watching the presentation about the new features introduced with version 11.6. in our RWS Community page. Starting from minute 9:00, the new export capabilities are explained.

This article is relevant:

WorldServer - why am I seeing the option 'Use cached Project TM' when exporting a project or Task to a Studio (WSXZ) package?
 

Also refer to this presentation in our RWS Community page.