There are many situations in which non-SPC coordinates are useful, but if your general question pertains to localization, for me it's a search tool. I often have the dimensions of a boundary, but the corners, distances and directions have no known relationship to the SPC grid. For purposes of localization it makes little difference if I calc those corners from an estimated (e.g. Google Earth) SPC-like position or from 15000,15000. Localization will make the connection between my search coordinates and the SPC grid for search purposes.
Going back to the reasons for using non-SPC: most of the boundaries I work on are referenced to something other than grid, typically a bearing base defined by monuments in the ground and a document of record. So I'll adjust my survey in Star*Net, and if the survey is on grid (much of my work doesn't involve GPS measurements at all) I'll instruct Star*Net to create a ground-scale points file that matches that bearing base. Whenever I do that, I make sure that those ground-scale coordinates are radically different from SPC (e.g. 15000,15000) so that they can't be mistaken for same.
The other common situation in which I use non-SPC coordinates is when I'm working on an existing project that's on a non-SPC grid (or on an older SPC epoch), in which case I'll match my work to the project grid.