I have overlay the experience fragment properties from this path(/libs/cq/experience-fragments/components/experiencefragment/cq:dialog/content/items/tabs/items/basic) to our project structure and introduce the new customized checkbox field in basic tab. So the checkbox available while we creating the experience fragments and it's available for all the experience fragments templates.
Could you please suggest, how to disable this customized checkbox field to some other experience fragment templates?
If you are not using main xfpage component as parent of the rest of templates then you can :
1.create one dialog in the child page component and add the field that you wanted to hide and
2. then add one property sling:hideResource = true.
this will hide that particular filed in the child dialog as in below image
If you are using one stand alone page component then you can simply skip the filed.
Hope this will help.
I would suggest to use sling:resourceSuperType=cq/experience-fragments/components/xfpage on all the custom XF templates (page components) and introduce the new customized checkbox field under that specific template (xf page component). Considering the custom xf page components are created under /apps/<your project>/components structure.
There are two nodes generated when a XF is created - main XF node and under that master variation node (other variations are added as well later).  has sling:resourceType always as cq/experience-fragments/components/experiencefragment while  has the sling:resourceType as cq/experience-fragments/components/xfpage or as per the template chosen.
I suggest you to add your custom field in the node  properties and not on node  by overlaying /libs/cq/experience-fragments/components/experiencefragment as it is same for all the XFs irrespective of the variation/ template chosen.
In case your requirement is specifically to add custom field in node  then you can leverage granite:renderCondition