More deeply telling usages view

Any thoughts about extending sticky lines to preview code views such as the code views shown in the “Preview Source” option of the usages view ― the view that opens when invoking the “show usages” feature?

Or, alternatively, making the method name optionally appear in each usage line in the mentioned view, without having to hover each usage line for seeing it when the “file structure” option is enabled?

Conversely, could the “Open in File Tool” option of the same modal window ― which already shows the entire file structure ― offer the option of seeing a source preview as a bottom pane rather than a column pane? 

Making quick deep sense of where functionally a symbol is being used could be further fast-tracked with any of the above suggestions, IMO.

Somehow juggling between both the initial and the File Tool view of the usages search feature, I'm not as productive in refactoring workflows which hinge much (for me) on using this feature for analyzing all usages, sometimes quite heavily and iteratively. 

It feels specifically for me like the said feature stops one step too early by not having that additional information even more readily available, I estimate I'd be x3 - x5 faster on intense deep refactoring work with this kind of enhancement, myself.