> Hank will detect and warn you about valid parts of your code that could potentially be deleted or at least refactored based on rules.

The place I work runs a heterogeneous erlang cluster (cluster-as-service-mesh), I assume the best way to deal with this is to mark off that module, or the specific cluster exports, to be ignored.

I imagine this tool also has a hard time identifying function invocations via erlang:apply

I don't think you're forced to act on anything that it finds; it just points you at things that might be removable cruft.