TMPGEnc's VCD templates: not VCD 2.0 compliant?

[Greycat]

VCDs I used to burn always played jerky from
time to time on my DVD player (quick fast-forward
and/or slow motion effects every 5 minutos or so).
I searched this forum to see if someone had the
same problem and found a lot of people like me --
and a lot of suggestions to solve the problem.
I tried every one and *no* success at all.

Then I found this page:

https://www.videohelp.com/VCD2TK_TMPGEnc.htm

I followed its "recipe" and that jerky problem
simply disappeared! No more annoying fast-foward
and/or slow motion effects whatsoever! Phew!

Only one little problem appeared: CDDAO always
performs an auto-padding, adding more or less 1 MB
to my mpegs. But as far as I can see, this doesn't
cause any problem to the playback, but I wonder
why the auto-padding is performed if that page says
the resulting muxed files are totally VCD 2.0 compliant...

I thought it was because my MPEGs are all 23.97 fps,
but I tried with 29.97 fps clips and the
auto-padding is still performed.

Anyway, have anyone tried this solution
or have something against it?
For me it really works.

BTW, VCDMUX (the demuxer that comes with
VCD TOOLKIT) creates .MMD files, which
VCDEasy doesn't recognize. But TSCV does,
and I believe there's no problem renaming
the extension to .MPG for VCDEasy (although
I always author my XML files "by hand" and only
use TSCV's tools to burn the VCD directly.

[secretagent]

that guide must be old. you can easily load the file in tpmgenc and select encode as elementary streams and it will output seperate mpa and mv streams at one time

[Greycat]

But VCD 2.0 standards remain the same.
The main point I want to discuss is that TMPGEnc templates and muxer (according to that guide) aren't totally VCD 2.0 compliant and the fact that following its directions made my VCDs "jerky-free" when
playing on standalone DVD players -- a problem that a lot of people
have reported in this forum for a long time.

Also I want to know why the auto-padding occurs with the
files created by this method (which should be totally VCD 2.0
compliant)