Hi Chris, a few notes on where I’m currently at as another long time GhPython user: I’m still using GhPython in Rhino 8/9 for production and likely will be until we start using Grasshopper 2. The main reason being that the new IronPython component is still not at feature parity with GhPython. I’ve lost track over the years, but from a quick search some primary issues are/were:
- Missing / broken SDK modes
- Missing enter and exit methods
- Missing component docstring system
- Missing mutable code property
- Worse output window performance
- Worse compute performance
- Worse syntax highlighting
- Verbose menu design
- More functional/design issues
In addition to a general feeling of work-in-progress jankiness that, while certainly exciting, doesn’t lend itself super well to getting the job done on a daily basis. The unknown unknowns and such 
Edit: That is to say, you might not be able to translate all your GhPython components (yet) and they might perform worse than they did in GhPython. Either way, I’d be interested in hearing about your experiences once you get going with the porting.