Solution 1:

The AcrylicHosts.txt file is reloaded each time the Acrylic service starts.

AFAIK the only other caches involved are the DNS client cache, which can be invalidated by the 1ipconfig /flushdns1 command, and, eventually, your browser's own DNS cache.

For example in Chrome you can access its contents by navigating to:

chrome://net-internals/#dns