Ahhh... more research! I went ahead and bought Profiler... after talking with the folks at Shades of Paper they seemed to think it would suit my particular needs a little better. Now, there is a trick (which I haven't tried yet) but I called X-Rite and what they said to do is use ColorPort to read in the chart and once you're done with the chart you can do a save as Monaco Session. After you've done that you can go into Profiler and select "Open Session". That will give you access to any amount of patches you want using Monaco Profiler. So, the good news is, it's possible. Bad news is I'll have to regen, and rescan my targets but at least it's doable.
ColorPort only exports Monaco data for color patches usable by Profiler. It gives you the flexibility to measure layouts not supported by Profiler, but the patch values need to be correct. Profiler requires the target RGB values to be at specific values. Unfortunately, none of the Atkinson RGB targets have values that follow these spacings exactly. Bill has an AppleScript that extracts the Monaco data, although the reference RGB values are not necessarily quite what was printed. For many measured values, the profiling software will be assuming the target was 1 RGB value off what was actually printed. For example, on the 1728 patch target, the print was made using RGB values of (232, 232, 232), while MonacoProfiler assumes the input was (231, 231, 231). Likewise on the 729 patch target, Profiler assumes you printed (95, 95, 95) while the actual value was (96, 96, 96). For most printers, the error induced by this rounding will range from negligible for some colors to ~1 DE for others.
Bill's 729 and 1728 patch RGB targets can be exported to MonacoProfiler with the above caveats about less-than-perfect accuracy. The 1452 target, however, does not contain the required patch data for any of the supported Profiler targets.
ProfileMaker does not require specific input values - you can feed it anything you choose. I do not recommend using the 1728 RGB patch target with ProfileMaker as it does not contain patch values near the midpoint of the RGB range; i.e. no values near 127. The midpoint is bracketed with values of 116 and 139. Depending on the printer output and linearity, ProfileMaker's algorithms often do not play well with this, making for problems obtaining decently neutral values.
Note: All of Bill's RGB targets use 16-bit images and the reference files contain fractional (i.e. 16-bit as well) RGB values. Depending on the application you use for printing the targets, your operating system, and the printer and driver, the images may be converted to 8-bits by the time they hit the printer. This introduces up to half an RGB unit of error between reference file and printed value. Whether the profiling application also allows 16-bit reference values depends on the app. If my memory is any good, ProfileMaker will. MonacoProfiler does not.
Bill's targets can be useful, but you need to be aware that there can be errors introduced by the format of the targets and how well the target values match up with what your profiling application expects.