It's almost as if there are technical reasons for not supporting the current extension api on mobile! (Battery, performance, ...)
Potential problems could be mitigated pretty easily by warning about or throttling extensions that use too much CPU/memory on mobile.
Not allowing extensions on Chrome for Android might have been an acceptable excuse in the early days of Android, with very weak single core CPUs. But not for years.
Also, even though you can run Android apps and Linux containers these days, Chrome OS is still built around using the browser in a way Android is not. Your phone has to balance the needs of the browser against other demands and apps.
It’s all trade offs....