This is critically important in this age where 3CX is often on the public Internet. We get a *lot* of attack attempts, and have seen other vendors get bitten by these drive-by attacks on 3CX.
2-FA is most important for the extension logins themselves. Where we've seen successful penetrations into extension logins is to make outbound toll-calls. 2-FA email verification for 3CXPhone installation (with a mac-address whitelist once auth successful so you only have to do it once per device), and 2-FA email verification with a mac-address or installation-ID whitelist for web login would basically solve this issue permanently.
This is how most remote access tools work - you sign in the first time and are prompted to check your email for the verification link to authorize the install. Sure, Google Authenticator or Office365 account federation would be nice, but email 2-fa is still much more secure than no 2-fa, and easy to implement, as all the pieces are already there in 3CX to make this work.