I added the options
--fix-gcp and --use-lon-lat-height-gcp-error to jitter_solve, with the same logic as for bundle_adjustment. This will be in tomorrow's build.
Solving for intrinsics in the jitter solver would require a large amount of code work, as there's a lot of book-keeping involved in the bundle_adjust logic for that (and many controls for how fine-grained the sharing of intrinsics should be). It would be a big undertaking to factor out that bundle_adjust code and then call it also in the jitter solver.
For now, if you are not doing that already, one can pass the lists of images and cameras as output by each of these tools to the other tool via --image-list and --camera-list.
BTW, recently I added some more options to the dem2gcp program (as documented in the news). This is quite handy when fixing local horizontal registration errors. Particularly the newer option --max-disp for this program is of help when too much changed on the ground and a DEM-to-DEM disparity (and corresponding GCP) ends up having inaccurate portions.