Understand your frustrations, but lets compete two things, hypotheses, here. One, that, according to Support, your iOS install is good, no issue. Then, another support diagnostic, that your battery is fine. Consequently, chose one Support opinion as fact and dismiss another Support assessment as mistaken.. If you do, all bets are off. To your own statements, no one in Apple Support confirmed that you have bad code shutting you specifically, at 20%..
"my battery life is perfect." You just stated shutdowns. How can that be perfect? If I miss an important morning appointment as my phone shut off at 20%, how could I call that perfect? Shutdown normally are a CB trigger, module, power SHUTS OFF. electrons stop moving. Lights out. Battery life includes every nanosecond electrons keep moving.
And if the forum is about drain, and your battery life is perfect, why come here? Seek the iPhone shutdown forum..
Glitches- that was said- firmware. Some had a firmware fix. Stated it numerous times, but it happened rarely here. Glitches happen. It is known. Why would one suggest RESET? because it works? A poor straw-men fallacy assigning statements I never made.
Deduction, not speculation- shutdowns are never good. Since the first days I built a system, it is a 101 lesson: inexplicable shutdown are never good. Almost always, odds speaking, hardware. Yes, have seen rare apps causing a shutdown, and one Reset does it. But in your case NOTHING DOES IT. E.G. you pretty much self eliminate any coding as cause.
It is unlikely that you understand, or appreciate, how sophisticated this Apple hardware is. Even the battery, a micro computer within a computer. More power than all the Apollo Mission modules, and each had a couch worth of battery to power tiny calculations. It is also unlikely that you studied, in any fashion, electrical circuits, let alone built one, but here you are, discussing what Apple programmers do in their office..