Actually, the appropriate place for the final ask is in the bug tracker on gitlab. The devs use the same mechanism to track bugs as they do for features. See this FAQ:
But what this forum area is useful is a sounding board among us users to help develop a feature request from an idea with ad-hock jargon to a proposal with KiCad and/or industry standard jargon.
For example, what I think you are asking is for an IPC (the standard that @Rene_Poschl and his library team strive to follow) calculator interface. (Sorry, Rene, I forget the standard number and version off the top of my head…) Or maybe for one of the other competing standards?
I don’t know the legalities of publishing and freely distributing a footprint calculator based off of a standard that has to be purchased to read… I’m not a lawyer so I’m not even going to pretend to be one.
There are some footprint wizards that are provided with KiCad. In the footprint editor see the “Create Footprint…” item in the File menu, or the 2nd toolbar icon from the left (looks like an IC with a star on it).
While they are mainly suitable for standard packages, one could use them for the pad/drill dimensions and then move the pads around to the correct position for a non-standard package.
I originally planned to convert them into footprint wizards but the KiCad wizard interface is just not powerful enough to encode the possible combinations for imputing part dimensions properly (The script is written such that you will not find a datasheet that does not map directly to one of the options available as we don’t want contributors to manually calculate any dimension).