The obvious benefits of the pool was not having to have inneficiencies in calculating the RC you want to delegate to someone. Not everyone is active every day so less RC would be needed to support more users. The second benefit was it could end up being less blockchain transactions than the alternative which I'll describe below... but the point is it does seem like there are alternatives which is a good thing.

questions

1. Is there a cool down for undelegating RC?
2. How much is the relative RC cost of doing a direct RC delegation to a user? Like what kind of transaction do you envision it to be?
3. If we take the old steemit example and delegated 15hp worth of RC what percentage comparison would delegating and undelegating take? Tiny fraction or something like 1-2%?
4. Continuing that example if we can delegate to a new user the moment they login to our site then maybe we can undelegate after x amount of hours or days away to free up that RC for the next new user. This example is the alternative that keeps limited RC more efficiently distributed but as you see it is a lot more hive blockchain transactions in order to manage it.
5. Trailing delegations is of course awesome together with posting authority to piggy back on those who want to help the cause. This does of course double the transaction overhead for each case.
   5b. So the sub question is do you see this being overwhelming at a certain point of daily users? At what point would it be problematic?

Cc @asgarth