Sorry for the late reply, I didn't have an internet connection for a while.
I don't think that there's a good remedy for it as of yet. I looked around for reasons why this runs in FCEUX at all, when it shouldn't, and it turns out that a fix for KT-008 boards is coded into FCEUX's MMC3 support with the understanding that they're often mislabeled as Mapper 4. https://github.com/TASVideos/fceux/blob/5be92d3ee50fcdc04ec4d727cef5201fa8fba378/src/boards/mmc3.cpp
It's ugly but you may have to have an IPS for a NES 2.0 mapper 224 header that makes it work in Mesen and possibly some other emulators, and an IPS for an incorrect but still playable iNES mapper 4 header that makes it work in FCEUX and maybe other FCEUX-based emulators.
While I prefer Mesen and understand it to be superior in debugging and hardware-accuracy, FCEUX is undoubtedly popular and has many ports (it even came installed on my little Chinese handheld) and supporting it is important, as much of a headache as it may be.
Anyway: The text pointers, from what I've seen by relative searching for the offsets of what I believe are string terminators (0D 0A), appear to be the offset (minus 10h from the header since I forget that often) + 8000h. For example, at 0606 these 2-byte pointers exist: 478D,538D,6E8D,9E8D,DD8D,EA8D,338E,3F8E,7C8E,DF8E. They lead to 0D47, 0D53, 0D6E, 0D9E, 0DDD, 0DEA, 0E33, 0E3F, 0E7C, 0EDF if I'm correct. Hope this helps.