Limit of SCSI Disks in Capability Profiles

It would appear that we have found a hard-coded limit in the Capability Profiles for the Maximum Number of SCSI disks. Every time we try to deploy a VM using a VM Template that has 5 SCSI Disks in it to a Cloud, we get the following error during the placement phase:

The operation on virtual machine, template or hardware configuration with id [TESTmachine] does not result in a SCSI adapter count between 0 and 4 required by the specified cloud and fabric capability.
Ensure a SCSI adapter count between 0 and 4 and try the operation again.
ID: 23437

If we choose to deploy directly to the host server (instead of choosing the cloud that has exact same host server in it) it works fine. The above error seems to point to the Capability Profile having a restriction on the number of SCSI Disks (it says SCSI adapters, but we only have 1 SCSI adapter, and we have 5 SCSI disks, so I believe the error message actually mean disks). If you open Capability Profiles in the GUI it doesn't lists SCSI disks (or adapters) at all. A copy of the default Hyper-V profile (so it is read/write since the original is read only) doesn't have the SCSI disks field either. We found that if we used powershell to list the capability profile, it does show a property called "SCSIAdapterCountMaximum". We used the following powershell command to list the properties:

Get-SCCapabilityProfile | where-object {$_.Name -eq "Hyper-V (More SCSI Disks)"}

We tried to change the property using the following powershell command but it doesn't allow us to.

$profile = Get-SCCapabilityProfile | where-object {$_.Name -eq "Hyper-V (More SCSI Disks)"};
$profile.SCSIAdapterCountMaximum = 10

Here is the error we get back:

"SCSIAdapterCountMaximum" is a ReadOnly property.
At line:1 char:10
+ $profile. <<<< SCSIAdapterCountMaximum = 10
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException

We can't find the property in the SQL DB anywhere either. It appears it is getting that property from somewhere other than SQL, and we cannot seem to set it though powershell. Does anyone have any ideas on how we can change this maximum?