Thanks for the break out. Let me go line by line.
Mobile - Outlook for Android - This syncs with its own separate API and looking at service telemetry and broad experiences you should be experiencing things well here. Again I would remove and readd the account. Don't try to manually force a protocol just let it set itself up naturally and it should set the proper config and be mondern auth/OAuth.
Personal - Outlook 2013 - OAuth is not supported, and setting registry keys likely can cause other impacts. I would recommend not doing that for this client. If you continue to use this client, you will need to stick with Basic Auth and as mentioend you likely will see an increased level of auth promptness.
Work - 2308 / 16731 - This is our Semi Annual Channel and this should be working just fine and if autoconfigured be properly setup. Gabe likely can assist a bit more here, or better yet would likely be to open an in app support ticket so that the support team can check config for the account in the logs.
For the other clients that you listed, Thunderbird recently just made a chance with how they setup the client. I personally have been communicating with their engineering team and we have discussed changes that were needed in their autoconfig service. They rolled out recently. The instructions that were also in the known issue shows the steps if you want to manually config. I can confirm that I have also had issues previously but when switched to OAuth my experience has been solid.