As usual, you need to detail the circumstances of both these issues better. Personally, I have not encountered the FX tail issue for quite some time, though it has been a problem in the past. It might depend on a particular combination of preference settings (esp. Always Stream Audio Through FX), specific FX used, bounce settings project architecture and bounce procedures.
 
I'm not clearly understanding the second issue but if there is signal on the track selected to receive the bounce, that signal could easily be included in the bounced audio, depending on your bounce options. For example, if you have nothing selected, nothing muted, everything routed to the Master bus, and bounce with Source = Buses, and Master bus selected, any pre-existing audio source on the target track will be included in the bounced audio. Nothing surprising about that.

Beepster
 
No one... at all... agreed to anything of the sort.

Frankly Beepster, I feel that's a little harsh. I think we can all agree he believes he's experiencing some kind of issue, and that no one else has been able to reproduce it.

The tail thing is not a bug. It's the way the audio buffers have always worked. You must select a range to bounce (or export) that includes the tail. While you can tell Sonar how long a normal tail will be, that's simply an estimate. Before I bounce, I always playback the midi until the tail is silent. That's the end of my range.
 
I thought that there was a setting somewhere to dump the buffers before each bounce (or playback), but I can't find it...
 
Regards,
Dan

As much as I hate to agree with Mr. Copper this is an annoying issue to deal with. It should be fixed. That little bit of audio that can show up at the beginning of a new audio track.  

I normally slip edit it out. 

That's not quite the same: again, from memory, toggling the audio engine flushes buffers; pressing space (start/stop) doesn't necessarily and/or might just load the buffers with *new* audio data...

KPerry
I actually had this happen years ago and serendipitously ended up with an amazing delay effect at the start of a track that stayed in the final version...

You are not alone; below is a similar post from a long thread about this issue that dates back to X1:
 
http://forum.cakewalk.com/FindPost/2385959
 
In my recent experience, there are cases where a buffered tail will play back at the start after rewinding (e.g. Clip FX tails), but for whatever reason, I haven't had a problem with them being printed to a bounce for a long time - maybe because it's plugin-specific. Per this old thread, the Sonitus DX FX are prone to this.

No this is not what I would call a tail. Its an unflushed buffer that will hold over to the beginning of a new track. Its a blip on the track. 

You can select a region longer than a midi clip. The bounced audio will be as long as the selection. Even a hundred measures longer (just did it). Besides, the answer to the OP is to use the new synth record option. Folks asked for this and I could never understand why they didn't just freeze. Mr. Copper's problem seems to be what this new feature is all about.

I understand and agree. For every upgrade Twelve Tone or Cakewalk has ever released since "Pro Audio" my biggest problems have been trying to work on old projects in the new software.
 That being said; the way you have described your workflow, I believe you would benefit from K. As opposed to "freeze" record synth doesn't disable the VST. You can solo the specific group of tracks you want to create an audio clip of, select a region and punch record that part. Then move the resulting clip to a new track and record another group of tracks.
 I'm not trying to sell Kingston to you. You've paid for it already. I do believe however, you will ultimately be more satisfied with K than H. I am.