My understanding is the key rules are:
1) wait for an operator and do not hang up (because if you hang up they assume something bad happened and will send police/fire/etc to you), and,
2) tell them that it is a test call so that they can assess whether they can spend time on you or should hang up to answer a more urgent call.
I'm sure kids call 911 enough as a prank that your test call won't have a meaningful impact on call volume.
It leads me to wonder if your comment about capacity (which I assumed was the case as well) does not apply evenly everywhere.
So, IMO, that the system isn't meant to handle this type of false alarm isn't reflective of call center capacity but rather fire/police/ambulance capacity (and also annoying everyone involved).
Now on the other hand, don't be a jerk. They're busy at certain times of day and they kinda expect people to make test calls during relatively boring business hours but not during rush hour or at bar close time. Don't be making test calls while a hurricane is hitting the city or while a t-storm is passing thru or a presidential visit or wildfires are kinda nearby, etc.
I've done this helping out as part of PBX installs (admittedly a long time ago) and just be calm and clear and polite when verifying the address routing and remember to say "thanks" and its not a big deal.
That is quite a bit off, there are ~3650 days in a decade. If you really wanted to use round numbers, would 5K not have been a better choice?
Also I forgot to mention I used small biz pbx as the most populous estimate because I assumed j.random.ATT cellphone user wouldn't test, one iphone should do about the same as the next