Your problem lies in trying to oversimplify the sums ... RPM is a major contributor but not necessarily in a simply encoded manner.
The airframe manufacturers generally use a detailed computer program based on engine OEM code to generate the thrust data .... trying to put it into a simple fn(RPM) relationship just isn't going to cut it, I'm afraid .. other than in respect of a rough first approximation.