Partly, and that's a fair comparison. Scorpion81's Fracture Modifier could break shards during a simulation, back on Blender 2.79, but it shipped as a patched build of Blender, not an add-on, the feature was marked work-in-progress, it never landed in mainline Blender, and its own documentation warned that 25+ shards could slow it to a crawl. TrickBoom does the same idea without Bullet at all, as an add-on that installs into 5.2.

No. Bake audio synthesises every hit, slide and fracture from the explosion in your scene, so there is nothing to license or download. If you prefer your own sounds, Impact markers and Export impacts (CSV) give you the frame, position and strength of every hit.

No. Nothing in TrickBoom touches Blender's rigid body system: no rigid body world, no solver to run, no point cache. It computes every shard's flight and writes it straight to keyframes, so there is no simulation for a render farm to re-run and nothing that goes stale when you move the file. The timeline scrubs backwards as fast as forwards.

Yes. What you get back is ordinary keyframed objects. Delete chunks, retime them, edit the curves in the Graph Editor, parent them to something else. TrickBoom hands you animation data and gets out of the way. Clear explosion puts the original object back whenever you want to start over.

Yes. Re-simulate flies the chunks already in the scene again with the current force, floor, seed, Physics sliders and collision, keeping your material and modifier edits on them. Every FX pass also runs against whatever explosion is already there, so you can re-roll one effect without re-exploding.

Blender 5.2.0 LTS or newer, on Windows, macOS or Linux. Every effect is geometry, materials and lights, so it works in any engine.