OK, so... I've figured out how Steam limits the games. Same function as Aali's 1998 driver (10001CB0) but without the customization - and the code is different. Aali's driver allows for customization of the minigame and battle swirl fps so is a simple 4 byte integer value (four records from a table). Steam does not.
As I feared, Steam minigames share a flat 30fps framerate value, used at 5c99201C [It's dynamic so changes]. The value is (1000 / 30 / 1000) as a double. This is fixable, because I can change the pointer to a different area of memory (that i use), and then update that address depending on which minigame is active. [The pointer also gets updated by adding the new offset to the Aali version. ]
The issue then is
1. This is more work to support the Steam FF7 minigames, when I want to concentrate on 1998 and not have to duplicate effort
2. This is not my problem, it's Steam's
3. This would work for the current (latest) Steam driver (AF3DN.p) only. Any different version (like from earlier or later release) would result in a crash.
4. It's dynamic and so all addresses change, so that would require even more work
Plainly, it's too much of my time to mess about like this. So, Weapon/Minigame updates are not supported for Steam version unless they fix their driver to change that value above depending on the minigame being used.
This is one of the big downsides to the Aali "driver" set up. Having to cater for it when it is modified or hijacks code you need to change.