Why should LO have an interest to switch to an OO core/library? Just to gain the OO name back and be present on the website? Tough deal. Also, I still think the code bases are too different by now [1] and there is little to gain.
Without at at least one 'consumer'/UI (which you do not want or cannot provide) there is little point in developing an OO core/library, or is it? Which leads to my snarky comment about end-users and their role...
The Open Office eco-system is larger, by far, than LO and AOO. Maybe LO may not benefit at all from a permissive licensed core (although it certainly has benefited from it, as noted elsewhere), but certainly other OO implementations might.
We have seen, and even the FSF admits it, that open standards do best with permissive licensed implementations. So if you want wide adoption of open standards, a permissive license is likely better.
The world is not just LO or AOO. After all, the enemy, so-to-speak, is this proprietary s/w called MSO...
Without at at least one 'consumer'/UI (which you do not want or cannot provide) there is little point in developing an OO core/library, or is it? Which leads to my snarky comment about end-users and their role...
[1] https://news.ycombinator.com/item?id=12413218