Sure, the makedumpfile(8) program has other uses, but we're talking about the dependencies of the linux-crashdump metapackage. There's really only one usage context that's relevant for that.
I wouldn't suggest dropping the makedumpfile package altogether in favor of makedumpfile-static, but dropping makedumpfile-static and putting a static binary in makedumpfile makes all the sense in the world. I've yet to hear any reason why one would need/want the dynamic binary when they already have a static one. This is a textbook example of a program that belongs in /bin rather than /usr/bin.