Kelley - so glad that you had a chance to check on this topic.
It’s been several days of normal running for that new Kobo loco, and I think that I can confidently say that changing cv49 from the default 19 to a value of 3 has made all the difference.
I’m still surprised that this particular oddity hasn’t been more prominent. Matt at ESU commented on the i/o groups forum that they have seen this behaviour before, and he recommended changing cv49.
Anyway, the topic got a lot of attention, and I suspect it further rounded out the knowledge base on potential unusual behaviours, so here’s hoping that it helps other folks who bump up against the same frustrations.