That’s merely code churn, which is not a good property. What you want in a codebase is something rigid enough to satisfy today’s constraints (including optimizing them) and flexible enough to be modified for some likely future prospects.

So for any current features, cost of fixing bugs and do trivial adjustments should be very low. But working on new things should have a great ROI, especially because what’s existing can be reused as a foundation.