Alternative approach: Find something that you care about and also that the business needs, and program that.
Downside is you have lots of uncomfortable conversations with your manager about how you're not doing what they said to do. You might get bad reviews, or fired, or threats of either. But you probably won't actually get fired because net positive programmers are surprisingly hard to come by.
Upside is you get to enjoy your work. Your skills grow instead of atrophying (or failing ever to develop at all). After a decade or two it's the difference between becoming a powerhouse senior IC, vs being an eternally junior programmer forced into management because you're too useless to justify a senior salary and anyway nobody trusts an old programmer who works for cheap.
For me there's only one possible choice. Autonomy, mastery, purpose, gotta have it.
I suspect that your 9 year plan is an unrealistic, best-case scenario, that won't come to pass.
Also, 9 years is a long time to survive if you're miserable. I think you may find that at some point, your employer and coworkers notice it, get sick of working with you, and replace you with someone else that really likes programming. Like a lot. But right now, not N years ago.
Guessing you FIRE hard? The rule is that people in this field upgrade their lifestyle, the exception is FIRE.