Hello Jason Siebert,
Based on the Microsoft documentation, /ppkg is a valid ScanState parameter and appears in the supported ScanState syntax alongside both StorePath and /i migration XML files. However, the documentation does not state that /ppkg can generate a provisioning package from arbitrary user-state captures selected only through custom migration XML, nor does it document the output semantics for the exact scenario you tested.
The key point is that Microsoft's provisioning-package documentation consistently describes the /ppkg workflow in the context of capturing desktop applications and customizations for recovery/OEM deployment scenarios, and those examples are tied to the provisioning-package capture process rather than general USMT state migration.
From the evidence you provided, ScanState successfully completed its primary operation because it returned exit code 0 and created a migration store at StorePath. Microsoft documents ScanState as a tool that scans, collects files and settings, and creates a store; the creation of the store therefore demonstrates successful migration-store generation.
I could not find Microsoft documentation stating that a .ppkg must be produced whenever /ppkg is specified, nor documentation that explicitly explains the combination of custom /i rules only, no /apps, exit 0, migration store present, but no PPKG output. The available documentation simply does not define that status combination.
Because you have preserved the run and do not plan to recapture, the supported diagnostic approach is to review the existing ScanState.log at verbosity level 4 and the generated file list for messages specifically referencing provisioning-package generation rather than migration-store creation. Microsoft identifies the ScanState log as the authoritative diagnostic artifact for command processing and migration operations.
My assessment is that the documented behavior clearly supports creation of the migration store in your command line, but the Microsoft sources I could verify do not explicitly document that /ppkg export is supported for a capture consisting solely of custom migration XML selections without the application-capture scenario that the provisioning-package guidance focuses on. If a definitive answer is required, this is one of the cases where Microsoft support would need to interpret the specific ScanState log because the published documentation does not define that exact output/status semantic.
If my answer is useful for you, please hit Accept the answer for me please.
HL.