Regarding problems with paying liquid hive to delegators, I have a similar problem with my community where the goal is never to power down the community account but at the same time we need some way to compensate community members for their support.
The compromise I thought was just delegating the accumulated HP from curation to another community curation account that powers down to access those liquid rewards. It may reduce the voting power for the community account but it doesn't affect the voting efficiency (provided the voting pattern doesn't change). The community gets to keep their HP without powering down, adds support to other community curation accounts (increase public relations), and answers the liquidity problem to compensate delegators.
I tested this on my community but it's a smaller sample compared to yours so results may differ.