I remember this soap opera in 2019. What I found disturbing and unprofessional was that each time you complied to some request a new problem was "found" by the maintainer, a wicked loop maximizing time waste. You were even too patient to re-push multiple times. You had implemented something new and important, and well tested, but the maintainer seemed focused to consider a problem a tab and a tag, before the identity certification requirement finally came out when all the "style" requests were satisfied and he went out of excuses to refuse.
Something similar happened to @NaDre (I hope the username is correct), he wrote extensively on it on this forum, when he pushed some patch to fix bug(s) of OpenVPN 2, but no merge followed and the bug stayed for years. Maybe Nadre can give us more details if he reads me.
I think this lack of professionalism could have discouraged external contributions to OpenVPN. No wonder we saw bugs haunting ovpn3 for years and years before AirVPN fork fixed them in few weeks. No wonder that important features of your forked library were implemented on the main branch with a delay of months or years (or never to date).
P.S.
The special authorization to let OpenVPN Inc. re-license arbitrarily anyone's contributions with any existing or future license may be disturbing and I can understand that you finally became reluctant to accept it.