100 tick wasn't tested at the time, no, at least on serveme.tf. It should be easier to run, still I'd plan for 50% higher CPU usage, which might be an issue on some machines and VPS-es. Server CPUs are typically many cores at lower clocks, and with HLDS/TF2-server being very single threaded that's an issue for (at least) HL matches at these higher tickrates.
Most people didn't feel 133 tick was a huge improvement, so I expect 100 tick to be at least equally underwhelming. Also, the bugs you describe are the same as for the 133 tick experiment, so the other ones are probably also still there, which I expect to be a deal breaker for the competitive community and leagues.
If you're looking to revive that experiment, I'd just aim for 133 tick instead. Let me know if you'd like a server set up for that in one of the serveme.tf / na.serveme.tf locations, that way you could try and organize some scrims to test it.