//hack = I have found a way around the problem that was probably necessary to use and could even be arguably clever under the circumstances where a hack is required Example: When I suggested using data uri as source of iframe to get around domain security restrictions in FF and still allow you to click on links and scroll in iframe which using about: uri scheme did not (long story involving national security and identity platforms)
//stupid hack = somewhat ugly thing I am doing to somewhat solve problem because I am perhaps not clever enough to think my way to solution at this time. Example - when I set the center of the map to be a couple decimal points of latitude off from where the address actually was because the designer wanted the address to be not in the center of the map, because then it would be covered by the search box, but slightly above the search box. Stupid because I bet there was another way to do it, also stupid because it was not exact and so we did not know exactly where the address was going to be drawn in relation to the search box, but we knew pretty closely where and that was good enough.
//stupid fucking hack = ugly thing I am doing that must be done to get around problems even though as well as being ugly it is also less than optimal in multiple ways, requirement for this hack caused by third party who have screwed us over by their very existence which makes me incredibly angry Example: put span around any text node inside of an element rendered by React using a Ref to get around the Google translate bug and similar problems.
Your definitions are entirely arbitrary and certainly not even remotely universally understood.
I'd much rather a comment that succinctly but thoroughly describes what is going on and why a hack is necessary.