Names can mean multiple things to different groups and if one had to cater to every group which finds a name non fitting then you'd end up spending more time on

Names can mean multiple things to different groups and if one had to cater to every group which finds a name non fitting then you'd end up spending more time on name changes than actual development as in some context any name can be seen as offensive. This isn't strictly useful and to non-native english speakers the connection between the offensive meaning and the name would most likely never occur as it's use in such is obscure (for one, this is where I first learned of it). Currently there's a large number of resources that refer to the program as GIMP which are unlikely to be updated if the name changed and thus making years worth of guides, tutorials, and so on harder to find unless you know to search for (which if you do... the name change is meaningless as you'll still see GIMP). Harassing GIMP over the name is hardly a way to get things moving forwards and only sparks a negative environment. Should you find the name to make the software unusable then it would be better to focus your attention on the fork which changes the name rather than continuing to contribute a negative to the positive news of GIMP turning 25.