While adding automated type detection was on of the early goals of the Runtime Converter, it has since become completely removed from the project's roadmap. One of the reasons that it was removed is that a much more important feature is the ability of the converted software to work exactly as it was intended to in the source language. To do this, it was important to make dynamic binding to function and method calls, so that the number of arguments could vary, as it does in PHP. That is not to say that it could not be done in some places to match method parameters exactly, but the complexity of doing so and making the project work is enormous, and that is not even automated type detection, only matching the number of parameters at compile time (which would have to be done before any type detection could be useful).
It is not very hard for a programmer to change dymamic to static typing via a manual evaluation of the code, and there is very significant assistance from the IDE. On the other hand, it is very hard for a programmer to fix a codebase with a thousand compile errors at once, or to fix a program that doesn't work the way they expected it to. So it is a "nice to have" feature, but not something really important to develop.
It may or may not be added to a future version.