Let us suppose we have a program which checks for orthodoxy according to the YouTube Terms of Service against each video submitted.
Nothing but a lack of having done the work prevents YouTube from adding to its "rejected" flag the following:
1) A list of timestarts and durations of the portions of the video violating the ToS. 2) For each item in that list, make it a tuple and add a reason -- which clause was violated?
Then outputting that to the owner of the rejected video.
Nothing stops them from doing this. Some set of words or images happened somewhere in the timestream -- the orthodoxy program has that timestamp as it churns through the video. And a specific clause was violated -- a particular word in a wordlist as an example, because there's no simple, non-composite function that just says "good or not good."
This is really not a particularly high bar as an ask.