Unreachable how? The producer would be implemented in-process and the consumer would be the stream connected to the service.
If you have slow consumers or if the producer can't publish/write entries fast enough I would assume the only reasonable thing to do is drop entries to not effect RPCs.
This is basically just to improve the ergonomics of using binlog, which Im not sure is worth the added complexity?
A smaller change and something we can implement ourself with the current interface is toggle the binlog with a settable/dynamic flags.
We would have to have an extra step for getting the locally written binlog out of the container but I guess that is not terrible.