Well, until I discovered Kstars / Ekos / INDI, I was using SGP for doing my observations / sequences.
Really, short of potential timing issues, Ekos is perfect for astrometry.
1. You need very accurate gotos
2. You need accurate plate solves / or plate solve info in the fits header.
3. You need very accurate system time.
The work flow involves acquisition / reduction / measurments.
In this case I'm going to be using Ekos / INDI for the acquisition and to help with the reduction as the astrometry.net solves are pretty accurate. For reduction and actual measurements you need a program like Astrometrica. It plates solves your images and gives sub arcsecond locations for each pixel along with some photometry. Fromt here you can do detailed measurements of any moving objects like asteroids and comets. But, the time in the fits header is critical. If this time is off by a few seconds or more, your measurements of faster moving asteroids (3 - 20 arcsec / min) will be horribly off. I made my own solution for this in C# with an SNTP client that syncs my system time, but if you are saying the time is coming from INDI now I'll have to find another solution to get the time accurate while obtaining asteroid observations. Having some sort of accurate time service server-side here would be awesome.
EDIT:
This looks like a quick and easy solution:
raspberrypi.tomasgreno.cz/ntp-client-and-server.html
Cheers!