Pynspect might take advantage of some optimizations
Based on #4214 (see attached profiles there) it seems there are a couple of hotspots in pynspect. It might make sense to look to the routines at the top of the trace (jpath_values, traverse, ...?) whether there's some low hanging fruit for optimization, or some apparent culprit (too much copying? "extend" instead of "for ... append"? too much isisinstance calls?).