Specifying per-table recovery mode
No, logging and recovery don't work at that level. What I recommend is, instead of trying to make one database serve two different recovery objectives, store this logging information in its own database (or a different, existing database) with alternate recovery objectives.

If that is not an option for some reason, the only thing you can really do to minimize the impact on the log is to:


Issue truncate instead of delete - which is still logged, but less so.
Instead of allowing for lots of small inserts, queue those up into batches and do what you can to make the eventual insert eligible for minimally logged transactions.