Updating system DLL versions and adding Binding Redirects

Has updating system DLLs used by Acumatica and adding binding redirects been a problem for anyone?   I’m considering updating and adding the following:

<dependentAssembly>
  <assemblyIdentity name="Microsoft.Bcl.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-10.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>

<dependentAssembly>
  <assemblyIdentity name="System.ClientModel" publicKeyToken="92742159e12e44c8"
culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-1.4.0.0" newVersion="1.4.0.0" />
</dependentAssembly>

<dependentAssembly>
  <assemblyIdentity name="Microsoft.Extensions.AI.Abstractions" publicKeyToken="31bf3856ad364e35" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-10.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>

<dependentAssembly>
  <assemblyIdentity name="Microsoft.Extensions.AI" publicKeyToken="31bf3856ad364e35" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-10.0.0.0" newVersion="10.0.0.0" />
</dependentAssembly>

<dependentAssembly>
  <assemblyIdentity name="System.Memory.Data" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-8.0.0.1" newVersion="8.0.0.1" />
</dependentAssembly>

Does anyone see a problem with this?