Maybe Pervasive could supply a P.SQL database file with the necessary information. The table could contain something like:
StatusCode - signed integer
Status Summary - char string (255 characters max?)
Status Description - variable length
The developer could then work out how to extract the explanation they need, or maybe the suggested API call would access it provided the table was installed under a predefined database name that you could predict was always going to be present (like the existing DEMODATA is....usually)?
Storing the information in a file would allow updated versions to be downloaded without the need for a service pack/update, plus the file could be used by older versions of Pervasive.SQL that have no chance of getting the new API call.
This is something I've been thinking of creating myself, but the thought of extracting the strings from the existing online documentation has always thrown a spanner in the works. That and having to keep checking whether new information has been added.