Looks like this fix broke using NativeList.AsDeferredJobArray() as parameters in IJobParallelForDefer jobs.

From Unity 2021.8f1 this results in errors accessing the array data in the jobs.

The following script reproduces the issue along with additional notes:
--
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using Unity.Collections;
using Unity.Jobs;
using Unity.Collections.LowLevel.Unsafe;

//Problem:
//A NativeArray<byte>.GetSubArray(odd_start, some_length) passed to a job will appear as not created and with a length of 0 inside the job.
//This only happens for a NativeArray of bytes. A NativeArray<short> and NativeArray<int> does not appear to show the problem.
//Additionally, the NativeArray<byte> must be created with ClearedMemory. UnitializedMemory does not reproduce the problem.
//Additionally the 'start' arguement to GetSubArray must be odd. An even value does not appear to reproduce the problem.

public class TestScript : MonoBehaviour {

private NativeArray<byte> byteArray;

private unsafe void Awake() {
//The problem does not occur if NativeArrayOptions.UnitializedMemory is set. Only if the byteArray clears memory (the default) does the problem occur.
byteArray = new NativeArray<byte>(1024, Allocator.Persistent);

//The following also reproduces the problem. The Unitialized memory part is OK, but the MemClear afterwards causes the problem the recur.
//Note the length of memory to clear must be even.
//byteArray = new NativeArray<byte>(1024, Allocator.Persistent, NativeArrayOptions.UninitializedMemory);
//UnsafeUtility.MemClear(byteArray.GetUnsafePtr<byte>(), 2); //Here, the length to clear must be even to reproduce the problem.
}

private void Update() {
TestJob job = new TestJob {
//If GetSubArray start is even, things are OK.
//If GetSubArray start is odd, the bytearray inside the job appears to be disposed or uninitialized.
data = byteArray.GetSubArray(1, 512) //length doesn't seem to matter. Start must be odd to reproduce the problem.
};
Debug.Log("A: job.data IsCreated=" + job.data.IsCreated); //job.data is OK as expected
job.Run(); // Inside run, the byteArray will appear as NOT created. This problem only happens if the first arg to GetSubArray above is odd and only if byteArray was created with cleared memory.
Debug.Log("B: job.data IsCreated=" + job.data.IsCreated); //job.data is still OK, which is interesting given it wasn't OK inside the job's Execute method.
//job.Schedule().Complete(); //Run vs Schedule makes no difference.
}

//BurstCompile doesn't seem to matter for problem reproduction
private struct TestJob : IJob {
[ReadOnly] public NativeArray<byte> data;

public void Execute() {
//if the byteArray were NativeArray<int> or NativeArray<short> everything would be OK.
Debug.Log("INSIDE: job.data IsCreated=" + data.IsCreated);
}
}

private void OnDisable() {
if (byteArray.IsCreated) byteArray.Dispose();
}
}