It's against US law to "enable access" or "make available" illegal content that's hosted elsewhere too (it's still considered copyright infringement), so your site cannot access/convert IPTV or other copyrighted streaming content that the user provides either. The high load was also the Lily app. It pegged the CPU at 100% and almost hung the server (in fact, it may have been the cause of a hang a few weeks ago, though I cannot verify that since I couldn't even log in at the time to see why the server was overloaded, it had to be restarted). That said, this app is way too heavy for Lily...a VPS is really the appropriate way to run something like this.
Here's a screenshot of your IIS process using 97% of the entire server's CPU from when you got suspended...it was like that for about a half hour before we suspended you.
That TempDuckUrls is indeed what triggered the porn detection. If that's just a cache, that's fine, it sounds like someone just went searching for that content and the cache kept the URLs. I didn't see any other mentions of adult content besides these, so just need to clear the cache.
To be unsuspended, you'll need to:
Remove the IPTV to video M3U functions (the other pieces of the tool that just provide non-video statistics like game scores and such should be fine to keep, it's the IPTV piece specifically that is a copyright issue)
Delete the proxy PHP file on the plesk account.
Make sure the image search tool doesn't cause excessive load, remove if load cannot be controlled. You'll probably need to ask to check your load on Lily since there isn't a way for you to see it like there is on Plesk.
Fix the content filter on the image search tool. You mentioned it's supposed to have one, getting it working should solve the porn issue.
Clear the TempDuckUrls cache.
Would you be good with that? If so, I'll give you 24 hours to do so.