On Mac OS, a custom CMM is used only if specifically requested and setup by an application. So the application needs to have a setting to select the cmm, or the documentation should clearly point out that the preferred CMM tag is obeyed, but ColorSync will always use the apple engine unless specifically instructed to do otherwise, regardless of the CMM tag in the profile.
Note that the preview app has a colorpreference where you can select the cmm, but it used to be inoperable, certainly not sticky, maybe not even applicable for all conversion possibilities in that app, in other words: clunky (read useless) implementation. This may have been improved in the latest version(s), although i highly doubt it...