What you could do is ingest the files into folders based on the {type} variable. This resolves to e.g. JPEG for jpeg files, for raw files it depends on the type of raw file. If you combine this with code replacements, I think you should be able to do exactly what you want.
I might be mis-remembering but I think you might have said in an older thread that PM treats the Jpg in Raw+Jpg pairs like a sidecar file and won't separate them using the {type} variable. I have not tried to figure out how to use {type} yet so I don't know if it works or not but I am going to try unless you tell me it won't work.
Aargh, you're right, the pair will end up at the same place. Sorry about that, I should have thought about this before suggesting.
Ok, I just tried it, took some snaps in Raw+Jpg and ran 2 ingests, one with Filter Files set to Raw only and one set to Non Raw only. It works, I can send the Jpgs to one folder and the Raws to a different folder. I set up Snapshots so I can switch the filter and folder settings fast for each file type. This solves my problem except that I am greedy and would prefer it if I could do this operation in one ingest instead of two! 
So please make this a continuing feature request.
Instead of two ingests, why don't you ingest everything and then run a move command on all files, moving the JPGS to a different place and leaving the RAW files in-place? This will likely require some trickery with code replacements and the filename variables, but it can be set up and is probably faster. A more advanced solution could be to create a “program” that does the file moving and add that as program to the list of editors, then you can right click a file and choose the action. I have done this for a number of tasks on my files (I'm on a Mac though and there converting a simple shell script into a program is easily done with Automator).
