Are you an anti-vaxxer as well? Because you're using the same logic that they use.
"It's not a problem anymore so we shouldn't have to do this and I resent being told what to do!"
It's not a problem anymore BECAUSE avoiding goto has become conventional wisdom.
If we start telling people that it's ok to use goto again, take a wild guess what will happen? We will go right back to the days of spaghetti code, except it will be that much worse now because software has become overwhelmingly more complex today compared to several decades ago.
The problem with self-described experts is that a lot of people think they're experts when in fact they are not, resulting in a hideous mash that some poor sap down the line has to somehow decipher.
It boils down to risk-reward. If there is a clear and overwhelming reason to use it, then go ahead. If not, then a convention control flow structure will be easier to debug, easier to maintain, and is less likely to cause an inadvertent bug because you jumped out of a code block without cleaning something up.