Revisit custom runtime API design

# Description
We need to discuss our approach to custom runtime APIs:
* Should we maintain single-storage APIs that essentially duplicate storage queries, in order to be able to isolate clients from storage changes?
* or, should we mainly limit custom APIs to views requiring multiple storage reads/combining multiple sources