nope. it makes aliases whether you like it or not. I never make an alias. if I have a field named THING, then run any geoprocess that results in copying that field over to a new feature class, now it has an alias, THING. If I then need to join the original THING field, or anything else with a field named THING, ARC will now show me 2 fields named THING, even though it already adjusted the newly added THING field to be THING_1.
ARCPRo field aliases are a mess.
Not only that, but if I do go in and fix the alias, it wont stay fixed. For example, if I open up the fields view, change the alias name, save, close, and go look at the table, its not fixed. if i close the table view and reopen it, sometimes its fixed. if I remove the table from the TOC entirely, and then add it back in, its not fixed anymore, it loses the fixed alias that I saved, and reverts back to the original alias.
This has wasted thousands of dollars of my time over the last several years..