I'm still a died-in-the-wool PSpice user.
I've dabbled with LTspice only because some of my clients wanted to
"play along" during their chip design.
Those who simply simulated my .CIR file got excellent correlation.
Those that chose to "draw" their own schematic got overly optimistic
results.
I mused for sometime over how Mike Engelhardt bragged about his speed
advantage over PSpice and every other simulator.
I went to one of his seminars and he touted over and over that his
technique of a special "compiling" of the netlist gave him the
advantage.
Then it dawned. His "compiling" is going in and replacing every
recognizable "standard" part in the netlist with idealized
equivalents. Thus the speed "improvement".
You can see his speed advantage fall apart if you feed LTspice with
only components not native to LTspice.
The absence of the Berkeley-Spice-standard .OUT file in LTspice
confirms my suspicions... that would list the actual circuit simulated
along with all the model data, operating points, etc, the whole
shebang.
As for model handling... any Berkeley-Spice-standard model should work
in LTspice (if not encrypted).
(The only way to avoid LTspice "compiling" is to run from another
schematic-capture-generated .CIR/.NET. If you run from a .ASC you get
the "treatment".)