Okay, I think there are a few reasons for that.
1. Most of the high level kivy users and devs are professional
developers with little spare time. It's one thing to help someone who is
stuck by spotting an error. It's another to comb through someone's
working code trying to guess optimizations when you don't know the
context and can't run the code without constructing an app to put it in.
And this class even requires constructing resources with it.
That is a lot of effort to help someone you don't know and the code
works: they are hunting for possibly minimal optimizations. Also
consider there are great tools for detecting inefficient code and
bottlenecks. Have you tried profiling it?
http://kivy.org/docs/api-kivy.app.html#profiling-with-on-start-and-on-stop
2. Kivy widgets and really built for interaction, and become quite
inefficient when using many of them as simple sprites. For that, you
should look at Kivent, a framework for building performant, dynamic
real-time scenes in
Kivy.
https://github.com/kivy/kivent
So, hope that helps and explains the radio silence? We try to be a helpful
bunch, but that confounded 24 hour limit thing is such a pain! :-)
Good luck