@Anonymous
Here is an answer to your question that hopefully you find helpful!
We could use Content library cleanup tool to remove content that is no longer associated with any package or application from a distribution point (orphaned content).
The tool only affects the content on the distribution point that we specify when we run the tool. The tool cannot remove content from the content library on the site server.
All things we have in the console with content (Applications, packages/programs, SUM deployment packages, OS Images, etc) will make a copy of the source in the Content Library.
The only way to safely remove content from the primary site's content library is to clean up the applications and packages in ConfigMgr itself.
If there is almost no orphaned content on our server. There is not much content removed from the distribution point, and we may see a message saying that no orphaned content can be released.
If the response is helpful, please click "Accept Answer"and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.