I thought there will be an object exported (via C or C++ API) for any client, not that cache is a property of every command
For example cache code could embed special monitoring class/object, update it locally, but when monitor port has been triggered, it collects all those monitoring objects and print them to client.

The same applies to thread queues - they might embed special structure, which is then collected by the monitor itself