Well Yes, why not??
Roon is fundamentally a Music Library Management, Integration and Delivery tool. If the Roon Library Cleanup is proposing to delete database entries or pointers, it is perfectly reasonable for a User to want to easily and quickly know what source or target objects are involved. How can that not be so?
Feature Requests is a stream where Roon Users can post requests for changes or additional features that they would like to see made available. The only appropriate responses from other Roon Users are to say “Yes, that would be good, I also vote for this”, or to post a method of doing what is requested or a workaround.
I do not understand why you would go into battle to put down a reasonable request and to argue against it, unless the request fundamentally changes the way Roon works in other aspects such that Roon is degraded.
It is up to Roon staff to determine if a Feature Request is worthy of consideration and implementation, not other Users, and it is puzzling why you would take it upon yourself to effectively attack what to me and others, seems a perfectly reasonable function. How easy or difficult to implement the feature is technically is irrelevant, and is up to Roon Devs to resolve, not Roon users to challenge other Roon Users on.
Why on earth should Roon not make it easy and automatic to get a list of deletions to enable User investigation/remediation? If you have a workaround, fair enough, post the helpful response, it there is a feature that does what the OP is requesting but he has not discovered it and you know how to do it, fair enough - post the helpful response. If you don’t want or need such a feature, fair enough, just move on.