Yep, it was PS in the url. For future reference for other's info, here is what my hosting said:
Looking into the way XenForo Formats the Thread's URL - A Mod_Security rule would indeed block the post to that thread or any other thread because it's URL has "/ps-" Which in some way or another is a way of a Web Attack Injection method according to a Mod_Security.
Going deeper into the issue brought me to a Drupal issue which happens on a POST http Command as well using "ps" in the URL, They experience an Apache 403 Forbidden but XenForo has it's own error handling for customization within the forum hence why we see it as "Not Implemented" With the command it was attempting to use "POST"
ps is a unix command for showing processes, We in the datacenter environment utilize that command to see what processes are running on a system, and shows resource usage as well.
It would be a good point in direction as you would not be accessing any "ps" command on the server as you are on a shared system, with that being said we can always attempt to whitelist "ps" to see if the error triggers the mod_security rule.