It certainly sounds to me like you would be an excellent “consulting engineer” or “consulting architect” on any sort of project.   You could be as busy as you care to be.

It might be most useful for you to think about what you don’t like, because these seem to be fairly specific things.   They seem to be, perhaps not so much reflective of a dislike of the work itself, but rather, dislike of certain environments or situations that you have found yourself in recently.   Or perhaps you simply want to broaden your horizons.

That should be easy to do.   If you have been writing code for 30 years, it becomes less essential that you actually be the one who writes the code, because your skill and experience might be better put toward choosing what code should be written, by whom and at what time; how the code should be tested and then deployed, and so on.   “Coders” can be had, who will work under your direction or according to your master plan.   The best use of experience at this level is really that of “executive.”