I believe he is referring to the changes to custom json costs and other resource credit changes. Resourse credits were implemented in a minimum viable product back on Steem but never re-addressed. The problem is it doesn't scale, it mostly affects low HP users, and that's it. Right now we have 2-4M custom json ops per day, this accounts for around 23-50 ops per second. This is a big chunk of the current daily ops. So re-evaluating their RC costs first is a good start.
As for RC Pools, last I spoke of it it was good to go in this hard fork, I haven't asked about it recently so I am not 100% sure.
That being said, RC are not consensus, so they do not need a hard fork for RC pools to be implemented.