While you can create segments to try and compensate for this, I don't know if Adobe can support a rule such as "over X hits within Y minutes"... because unfortunately, segments are based on Hit, Visit or Visitor logic... and you don't want to exclude all traffic from a visit or visitor.
Also, the time boxing in a segment is more about hits that happen between certain dates...
But, you still might be able to get creative with your segments... I don't know enough about what is happening on those inflated calls... but in the past, I have created rules that excluded inflated hits due to an "infinite reload" issue on tablets (or rather anything that was at the breakpoint between tablet and desktop - this was our issue).
I basically created a rule that looked for:
Exclude Hit [
Reloads exists
AND
Mobile Screen Width equals 768
AND
Date Range x-y
]
This wasn't perfect.. and I would have lost some real traffic from earlier in the day before the issue started, and the end of the day after the issue was fixed...
However, you are dealing with videos, so you might not have a clear cut value to look at
Essentially, I excluded all the reloads for tablet within the time frame of the issue, but you may not have a value like reloads to use as a compensation...
But, maybe you could look at Video Views and Page Views? Using the number of Page Views as a limiter for the Video Views... you might cut out some legitimate "video views" from people pausing and restarting.. or maybe you have multiple videos per page..
But it's something to try and get those values under control.....
