When you use the runtime detection feature to add a soa-p 5.3.1 server it is detected as SOA-P version 5.2.

When you add the server manually, there is no server type soa-p, so there you have to choose EAP 5.x anyway and so this issue is not present there.