There is nothing that focuses on actually understanding the data and being able to edit or remix it, reorder it.
I think this is the key to the question: it needs more of an IA approach before treating it visually and is also very content specific. There isn't a catchall solution for displaying every type of data in a hub and spoke visualization.
Just for a thought experiment, let's take for example a hub and spoke visualization of someone's Facebook social network and the goal for the user is to get from him/herself to Kevin Bacon in the smallest number of clicks possible (let's put aside privacy issues and assume you have access to every friend of friend of friend and so on -- and that Kevin Bacon is in fact on Facebook and has friends). Furthermore, there is no quantum computing available that will automagically show you the best path based on some kind of algorithm.
Given that someone's social network could range drastically (let's say from 20 friends to 1000+), there will definitely need to be some kind of filtering mechanism to limit the connected nodes to a manageable data set (let's say 10). Furthermore the path the user takes and the data that is shown is dependent on which nodes are selected so there will have to be a method of selection and the dataset will change upon that selection.
Given the above, an acceptable UI would need to incorporate some kind of filtering mechanism or multiple filtering mechanisms on top of the hub and spoke node selection. Some natural options would be gender radio buttons (male/female/none), and age range slider, and keyword search filter that links to a user's Likes in their profile.
You can see that this dataset requires a lot of filtering as well as trial and error on the user's end. Let's compare this to another example:
Let's assume a data set of the tree of evolution from trilobites all the way to modern homosapien and every species that has ever lived on planet Earth (whether this is factual is irrelevant to the hypothetical). This hypothetical interactive graph is a teaching tool that allows student's to explore the connections between species freely. A simple scroll/pinch to zoom functionality can change the zoom level of the hub and spoke visualization while clicking and dragging or tapping and dragging allows the user to pan around at that zoom level.
Furthermore, at each zoom level, a maximum number of nodes can be shown (let's say 10 again to be consistent with the previous example). Depending on the zoom level, the nodes will display either the domain, kingdom, phylum, class, order, family, genus, or species appropriate to that zoom level.
In this example, there is no reason to filter options and no selected state that dictates what data is displayed next. There is no need for one. At the most, there may be a drop-down to select the zoom level based on the domain, kingdom, phylum, etc.
Given the two disparate datasets with their unique data connections, hierarchies, relevant data, and user goals, the UI would have to adapt to suit each. This doesn't even take into account data creation or node-connection creation.
I think it is our job as UX designers not to apply catchall solutions to unique problems, and conversely not create unique solutions to common problems, but to focus on the problem at hand and find a solution that works with the tools at hand. In the event a tool doesn't exist to solve the problem, or a better one can be fashioned to more efficiently (or more pleasurably) solve the problem, then our job extends to the creation of that tool.
There is no catchall design solution. This question requires the designer to first look at the unique dataset and the goals of the user before exploring design and functionality solutions.