Hi,
The three functions you would be interested in are occurrence(), predict(), and simulate().
Kriging in ctmm is done in continuous time, so irregular sampling is not an issue for any of the functions to operate correctly. If you want to predict where the individual was at a specific time, then the method you want is predict(). However, the autocorrelation structure of predictions is more smooth than the autocorrelation structure of real trajectories. If you want to regularize your data for an analysis that assumes even sampling, then you want to use simulate() many times, running the analysis many times to capture the uncertainty of not knowing where the individual was at the times of interest. However, you still do not want to use simulations too far from your data, as that will more reflect the movement model than the data.
occurrence() returns a distribution of where the animal might have been during the sampling period (or some range of times). Occurrence distributions of all kinds are sensitive to the sampling schedule by design. There are some gap skipping arguments in occurrence() that I just updated on GitHub. These are used to keep the occurrence distribution tight to the data, as large gaps will produce large blobs of uncertainty when you didn't know where the individual was... and people are usually not interested in visualizing that. If you want to compare occurrence distributions in an apples-to-apples away, you might consider tweaking the gap skipping arguments to make them more comparable, if possible. occurrence() doesn't return a trajectory, however. It is a distribution that (if I can steal a thought from John Fieberg) is more like the confidence intervals around the full trajectory.
I hope that answers your questions.
Best,
Chris