I'd like to also comment on here, the twitter addon indeed will not function nicely with the caching feature. Obviously because when cached, couch serves a html-created page of the template being called, rather than creating that html page on each request. This speeds up loading but means anything that may be different on that page (Any data that changes each day, or something like tweets, will not be updated) because the back-end isn't creating a new html page with the up-to-date data, thus you are left with out of date tweets and the newest ones only show when you save the template in admin (couch recreates the cached html page).
As far as I'm aware, no-caching a single template will NOT fix this issue, because the templates calling the twitter info from the no-cached template will still be showing the cached version of those templates. So, your html-created page within the cache does not re-call the template that isn't cached each time it is requested, thus the same problem persists.
To the best of my knowledge, this is how the couch cache works and so the solution won't fix the problem. I think your best option is to use a third-party javascript solution to implement your tweet functionality. Any javascript will (obviously) be the same on the cached version and will function the same, thus calling the data from twitter via the front-end rather than couch doing the work. I would recommend doing this over disabling the caching feature, because it increases performance a lot. You could turn up the rate at which couch automatically invalidates the cache and generates a new html page for its cache, but in my opinion there's a cut-off between how much it actually increases performance and how often it regenerates the cache.
Just my two-cents. Perhaps more like 5