(It's a facetious question: unless you're a $100B company you're not doing anything of the sort.)
That's not meant to be a snarky question, I genuinely don't understand what business problem that's going to be solved by saving at most 30 ms. Anything written in Rails/Django, talking to a DB, etc. is going to have request latency dominated by other parts of the stack.
I think it's misleading to say that deficiencies of Heroku have anything do to with AWS though. It's really, really easy to set up anycast [https://aws.amazon.com/global-accelerator/] with ECS [especially if you're willing to pay for Fargate]. If your product does something meaningfully different than that, I'd love to know more.
NB: I'm in no way affiliated with AWS or Heroku, just have experience with both in the past.
What do you mean by this? It seems pretty much on par with the expensive cloud pricing of the big players.