If you want precision tracking but not pointing, with the right SW you don't need to make a model with lots of points. You only take samples along the trajectory that you are going to image on, which is the optimal sample set. So suppose you are going to image a target at RA = 13 hrs and dec = 30 degrees. What you do is do test images and plate solves at RA=13hrs, RA=12h30m, RA=12h, RA=11h30min, etc which are just along the trajectory that the mount is going to follow, and then the SW implements precision tracking along that path and side of pier because it knows the mount errors for that one trajectory and it doesn't care about some other part of the sky where you are not imaging. I know that I've seen SW that does this but for the life of me I can't recall what it is.
I have Tpoint for my observatory mount and I've played with it but so far all I do is a 1 star align and then I plate solve near my target and re-sync. I actually do a "zero star" zenith initialization by pointing the OTA at zenith and measuring that with a level or a tilt sensor, I do the initial sync to that, then I go to something in the neighborhood of my target, focus, plate solve, and then I go to the target.
I have to say that one of my whinges is that we have variable axis rates in ASCOM but we don't have any way in ASCOM to move the model into the mount and there is no flag AFAIK to tell the planetarium SW if the mount is modeling or not. Normally variable rates are used to track comets and asteroids and shouldn't be used for modeling corrections because with modeling turned on, you want to report the on-sky coordinates and not the mechanical coordinates, but to make the model in the first place, you need to report mechanical coordinates. There's a "needs refraction" flag but no atmospheric data. If you want to do this via ASCOM you're better off making fake guide pulses to implement model-based precision tracking, and then of course you have to make that play nice with PEC if PEC is outside or inside the mount, and it could be in either place (PPEC for example is in PHD, not in the mount). That's one reason that you tend to have proprietary tracking correction solutions. OK rant over.