While authenticated encryption (AEAD) is good - especially for something like OpenPGP, which is an old and over-complicated standard that has a concerning large attack surface for vulnerabilities or simple implementation errors - I definitely can't recommend enabling a non-standardized compatibility-breaking feature by default, and frankly feel that GnuPG made a major error in doing so. If any of your systems are not using GnuPG specifically, or even are just using an older version of it, they can't be expected to implement a non-standard feature.
From a security perspective, I'm not even sure that just adding an OCB-based AEAD mode actually helps anything, in expectation; OpenPGP messages can already be authenticated in a few different ways, so arguably the likeliest source of security flaws is that the message format is too complex, not that it needs new features. If this mode replaced some of the other message authentication features that have been added over the years, that would be an improvement, but even then it really needs to be added to the standard before even considering turning it on by default.
Given that you work with non-GnuPG clients, and that this feature is not part of the OpenPGP specification, and that OpenPGP already includes message authentication and integrity, I recommend disabling this feature for now.
It's worth noting that you can disable it for an existing key, and later re-enable it, without needing to generate new keys. Also, this has nothing to do with RSA vs. ECC/Ed25519 keys; the key blob includes information about what features you (as a recipient, or rather your client) support, but the asymmetric key type used for signing and symmetric key exchange has nothing at all to do with the symmetric bulk encryption algorithm or mode of operation. If you generated a new RSA key right now it would also have this feature enabled, you could enable it on your old key if you wanted to, and you can (and IMO should) safely disable it on your existing key to restore compatibility with non-GPG clients. Note that you'll have to re-encrypt the data for non-GPG clients after disabling this non-standard feature.