While I would not have used the descriptor "dependencies", substitute that with the term "partners":

  Our service occasionally gets especially expensive requests 
  that amplify to our partners, one of those partners have 
  started complaining that our bursts of traffic are 
  impacting other users, talk to them and propose a solution 
  that aligns with our different requirements.

> The problem you proposed would be a mid level or senior dev type problem on most organizations' job role descriptions.

With the clarification above, I believe a junior dev could perform this task, even if the proposed solution is known to be a learning exercise.

The immediate value to the team is the collection of partner concerns.