I have an idea for a product that would monitor your code as it runs in production with the intent of identifying code that is no longer called. The tool would then open PRs on your codebase to:
1. add tracers to give confidence the code is truly unused, and; 2. remove the code no longer being used.
Obviously, security and performance would be paramount.
Is unused code something that your team is concerned about? Would this be something people would be willing to pay for on an ongoing basis?
You might have more luck building security tools in my opinion--that seems like a bigger implication of unused endpoints, code, etc -- maybe call your potential customers and ask what tools they need around that.
Not really, unused code is rarely a problem that businesses care about its unfortunately a user's problem.
I think businesses would care a lot more about code duplication. I can imagine a tool which uses fuzzy matching to find different levels of duplication in a codebase. It might even be an easier problem to solve.
But that's equivalent to solving the halting problem, which is impossible. So, no.