And as I spent the last two days hunting down a solution, I'll share it with you right away:
tl;dr: Use this cross platform & open source tool by the US Government (ya, really) to stick XMP Metadata in the WAV File.
WAV Files support the "cue " chunk, and this chunk is written by Audition, but I couldn't make it read from this chunk, and related chunks containing the cue names.
But Audition also writes the XMP Metadata, including a somewhat redundant copy of the Cue chunk. And it will also read it back.
So, by generating an XMP file containing the cue information, and sticking it in the XMP chunk of a WAV file, you can import that data to Audition.
<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.2-c003 61.141987, 2011/02/22-12:03:51 ">
The format should be self explanatory.
If you want to write your own tool to automate this, follow the XMP specs from Adobe concerning WAV files and the XMP chunk, which, ironically is named backwards:
The XMP in […] WAV is in a chunk with the ID "_PMX", encoded as UTF-8.
Note that the ID is backwards, due to a bug in the initial
implementation concerning processor byte order.
Here's an iOS App that will generate Audition-compatible XMP files: