I am the prinicipal developer of zapcc. We have added a FAQ
and more tech details in the cfe-dev mailing list
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2015-May/043174.h...
To the point, zapcc will not reprocess foo.h. This is a limitation. However, zapcc does deal with templates instantiations and such correctly and fast, such as boost various libraries, Eigen and LLVM source code.
For example, some might say that you can't automatically cache headers because of code like this:
// file1.cpp
#include "foo.h"
// file2.cpp
#define float double
#include "foo.h"
But if you're a bit clever about it you should be able to cache opportunistically and then detect if your cache is invalidated.