To answer your specific question of if there is a software tool to simulate something using nothing but the generally available technical specifications (in other words, stuff in the datasheet): no there is not. It is not possible to simulate nonlinear components using the datasheet. They do not include the needed information to construct an accurate model.
That said, you're already using the industry standard tool. SPICE. Microcap is using SPICE as its backend, and SPICE can simulate whatever you have models for, and the accuracy will be limited by those models (and in some situations, trtol). There is nothing to switch to, you're already using the simulation engine that is as good as the word of God. Do you think we design 14nm FinFETs interacting on a breadboard? Of course not. We model them (along with no small amount of quantum mechanical effects which begin to dominate, like tunnel injection) using SPICE. Then those simulations have sufficient predictive power that when we scale up those interactions to literally billions of transistors in a single circuit, spend millions (or billions) tooling up a fab to produce a CPU, guess what? It works. There are generally 1-2 revisions of a new Intel CPU before it's released, and always to improve yield. They always work on the first try though. The cost of one lithography mask is so high that you're allowed to screw up zero times. That is why I say SPICE (or internal tools based on it) is as good as the word of God: it is. Math works. It can never not.
Engineers who are suspicious of it are blaming their mistakes on the least likely link in the chain. SPICE simulates exactly what it is told - if you tell it garbage, you get garbage. You have to tell it something that can physically exist using verified empirical models before it will have useful predictive power.
Fortunately, this means you already have the tool you need. With this in mind, I'll tell you how to simulate PTC fuses, zeners, TVS diodes, all under overload conditions or transient surges.
So how would you go about simulating PTC fuse A vs PTC fuse B? You go about it exactly like simulating anything else in SPICE: Using PTC fuse A and B's respective SPICE models. Same with the zener diode. Or discharge tube. Or TVS diode. You should always use the model for the specific part number you plan to use.
Most SPICE simulators will include a built-in library but this is rarely going to be adequate and is really only there as a convenience. NEVER use ideal/unmarked components. If the zener diode doesn't have a specific part number you can enter on digikey and get a small selection of the same part to buy, it is not suitable for simulation of a real circuit. You can spot a generic/ideal component easily: It will instead of a real part number have none, and will include some basic parameters like breakdown voltage etc., things you'd see in a datasheet.
So you shouldn't even be looking for some generic PTC fuse in the library, and should not be using generic zener diodes (if you are). You must always simulate actual parts on your BOM using vendor supplied models for each one.
Littlefuse, Bourns, Vishay all supply SPICE models for their PTC fuses. That's just off the top of my head, but I would say most reputable vendors do so as well. They are usually in PSpice format which can be used by Microcap. You can even just copy and paste the .SUBCKT directly into your simulation as a SPICE directive. Microcap has a walk through in the documentation for adding 3rd party models. I'd advise becoming familiar with this task, as it is a vital one and one you will need to do often if you are planning on your simulations being useful except as a theoretical learning tool.
Now you might ask, "what if the PTC fuse part I'm using doesn't have a SPICE model? How to I simulate it then?" The answer is: you can't. Pick a new part with a model, or accept the trade-off of using the model-less part in exchange for not being able to simulate (with any useful predictive power) the circuit protection part of your circuit. I know that's not what you wanted to hear, but it's the hard realty unfortunately.
It is vitally important to use part-specific models for every component (except perhaps resistors, but make sure they have a Tc value for when things get hot) in a simulation of this nature. It wouldn't hurt to guesstimate parasitics from a real PCB layout and put those in as well, but you can probably get by without going that far.
I am guessing you want to verify the response time etc to an overload transient. This will depend heavily on part-specific capacitances and other empirically measured values for a given part, values that will be missing in a generic model.
The main purpose of pre-synthesis simulation is to verify the logical functionality of your design, without worrying about the specific timing details of a particular implementation.
This saves a lot of time in the functional debugging cycle, since you don't need to wait for the synthesis process to complete before simulating again after making a change.
Once you have the design working correctly with "nominal" or "unit" delays, you can then run the synthesis tools and verify that it continues to work with actual timing delays. Fixing the issues at this stage and dealing with long critical paths usually takes fewer iterations, which is good since each iteration takes longer.
But in fact, many designs are never taken through post-synthesis simulation. It is often sufficient to use pre-synthesis simulation to verify the functionality, and the static timing analysis tools to verify the post-synthesis timing.
Regarding your subsequent edit, if the order of blocking statements ever matters, then you're probably not doing something right.
One of the key differences between simulation and reality that I frequently trip over is the specification of sensitivity lists for processes. The simulator will always take the sensitivity list literally, because this is important with regard to making the simulator run efficiently. However, the synthesis tools and the actual hardware don't really care about sensitivity lists (although some synthesis tools will give you a warning if there seems to be a problem) — if a signal changes, those changes will propagate through the logic regardless of what the sensitivity list might say.
Best Answer
As far as I remember the SPICE algorithms you do not want its internal matrices dumped on you. Also I believe for transient analysis it converts all capacitors to voltage sources (and inductors to current sources) for every time step and solves the non-linear circuit like a DC one. So there are no true differential equations in SPICE.
That said, SPICE could output the transfer function of the circuit; IIRC as a list of polynomial coefficients. This sometimes suffers heavily from rounding errors but for simple circuits it may be what you are looking for.