I don't think so.
Looking at cpu_blit, that "blitter" has exactly a single function that's actually used, and it might as well have been a function on its own. I've twice pointed out how to avoid that situation, but for some reason you ignored that. In the case of cpu_blit I went along with that in the assumption that later patches would fix it, but I'm not having another implementation like that.