I've certainly not tried it. The problem with any kind of caching is that there's really no way for anything other than Fabrik to know whether a given list or form can be safely served from cache. The main J! site caching works, because that still calls the Fabrik controller, which can then make the determination as to whether a cached copy can be served. We invalidate the site cache for a given list or form if anything happens (within Fabrik) that might change the underlying data.
But most 3rd party caches, or J!'s own cache plugin, never call the component (be it Fabrik or anything else), and make the assumption that the data being served for a given set of request / post variables (like id, pagination, view, etc) is static. So if (say) &option=com_fabrik&view=list&listid=123&start123=20 has been served within the cache timeout period, then it can be served again out of the plugin's own cache. Obviously this isn't true for Fabrik, as there could be session filters, or a form could have been submitted which modifies the data, etc. And there's no way for us to invalidate the 3rd party's cache.
So really the only way to run a 3rd party cache is if it allows you to disable their caching for a given component, and add Fabrik to the exclude list. Which may or may not work if you use Fabrik modules and content plugins, rather than direct component links.
-- hugh